Securing a published site
Not every Confluence site should be public. Capable Sites can put a password or a sign-in in front of every page, so only the people you choose can read it. Access changes apply straight away, with no deploy, and cover staging previews too.
Remember that Confluence page restrictions do not carry over to a published site. Access covers the whole site. To keep one page private, keep it off the site.
#Common tasks
You want to | Go to |
|---|---|
Put one shared password on the site | |
Let people sign in with Google Workspace | |
Let people sign in with Microsoft 365 or Entra ID | |
Make the site private to your own people | |
End every visitor session now | |
Compare the five access modes | |
Understand who each sign-in lets in, and why visitors are refused | |
Fix a failed Access save |
#Guides in this section
#Related
Public by default. Private when you need it.
