for confluence cloud Is there any public/anonymous access feature at site/global level? If yes, does it take precedence over disabled anonymous access at space level?
How should global/site permissions influence ACLing? i.e intersection.
Hi @RoliT. There’s a nice Confluence Permissions: Best Practices docs page that describes many different scenarios, and the types of permissions settings you should use. It is for Server/DC; however, most of it should translate well to Confluence Cloud as well.
As for hierarchy of permissions, from highest level down, it is:
- Global permissions (across the entire Confluence instance)
- Space permissions (who can view/edit/manage content in a space)
- Page restrictions
Re: Nested spaces – no, spaces cannot be nested.
Re: Site-level permissions – yes, they exist. See docs on what are called Global Permissions (permissions that apply at the site/instance-level). Space-level permissions are only applicable to each space.
1 Like
@nmansilla
for confluence cloud Is there any public/anonymous access feature at site/global level? If yes, does it take precedence over disabled anonymous access at space level?
How should global/site permissions influence ACLing? i.e intersection.
If you set up anonymous access at the site/global level, it will allow non-logged-in users to access the Confluence site. It does not take precedence over space-level permissions. You’ll have to go into Space Permissions and allow for anonymous access for each individual space.