Feature spotlight
In This Blog
Syncing with an external Confluence site means trusting whoever’s on the other side with a live connection to your content. Left unchecked, anyone holding a valid sync token could start pulling from your space the moment they import it. No review, no record of who or why.
Whitelisting closes that gap.
Once enabled for a space, any external space trying to sync with it has to submit a request first, including a stated purpose, before the connection goes live.
As the space admin, you see the request and decide: approve it and syncing starts automatically, or reject it and nothing connects. Org and Confluence admins can also control which space admins are allowed to manage this themselves, space by space or across the board.
Picture a space admin maintaining documentation shared with several implementation partners. A new partner’s team requests sync access, stating it’s for a joint onboarding project. Instead of relying on the token exchange alone, the admin checks the stated purpose against an actual engagement and approves it — with a record of who requested access, when, and why.
This turns “we’re sharing content with an external site” from a leap of faith into a reviewed decision, without adding a new tool to manage separately.
Full setup steps — including how to turn on whitelisting for specific spaces or all spaces at once, and what the request/approval flow looks like from both sides — are in the whitelisting management guide and the requesting sync access guide.
Not using Space Sync yet? Start a free 30-day trial to see how it works for your team.