Restrict a published Confluence site to your company
To restrict a published Confluence site to your company, open the site's Settings, choose Access and pick the sign-in your people already use: Atlassian, Google or Microsoft. Then add your company's email domain, Google Workspace domain or Microsoft organisation and select Save changes. Anyone outside it is refused, and Confluence page restrictions play no part.
#Before you start
If your people use | Choose |
|---|---|
Google Workspace | Google, with your domains under Workspace domains |
Microsoft 365 or Entra ID | Microsoft, with your tenant under Organisations |
Atlassian accounts for Jira and Confluence | Atlassian, with your domains under Email domains |
You need to be a Confluence admin to change the mode.
Google and Microsoft check the organisation the account belongs to, which is stronger than matching an email address. Prefer them if your company uses either.
#Steps
Open Capable, choose Sites, open your site, and select Settings, then the Access card.
Under Who can view this site, select Atlassian, Google or Microsoft.
Add your company in the panel that opens: Email domains for Atlassian, Workspace domains for Google, or Organisations for Microsoft. Press Enter after each entry.
Under Sessions, choose Stay signed in for.
Select Save changes.
Open the site in a private window and sign in with a work account, then try a personal account to check it is refused.
#If it does not work
Anyone with an Atlassian account gets in. The Atlassian Email domains list is empty. Add your domain and save.
A colleague is refused. Check the domain or organisation on their account is listed. The Access denied page shows the account they used.
One page must stay private from colleagues too. Access covers the whole site. Keep that page off the site with the
capable-sites-excludelabel instead.
#Related
Your people in, everyone else out.
