What is the hierarchy of confluence cloud ACL?

[Roli T]

What is the hierarchy of confluence cloud ACL - can there be nested spaces?

I’m seeking clarification on how permissions work in Confluence Cloud. Specifically, I’d like to learn about the ACL (Access Control List) hierarchy and how permissions are configured. Here are my questions:

1. ACL Hierarchy: Could someone explain the Access Control List (ACL) hierarchy in Confluence Cloud? How are permissions structured from the top level down to specific content?

2. Nested Spaces: Can Confluence Cloud support nested spaces, and if so, how does this affect permissions? Do permissions apply hierarchically within nested spaces?

3. Site-Level Permissions: Are there site-level permissions in Confluence Cloud, and if yes, how do they differ from space-level permissions? Can site-level permissions override space-level permissions?

I appreciate any insights or documentation references that can help clarify

[Aron Gombas _Midori_]

The hierarchy is like this:

1. Site-level: you can invite users and give them access to various Atlassian products (some can only use Jira, others everything, for example).
2. Confluence-level: there are global permissions like "create space".
3. Space-level: there are permissions like "who can create a page in this space".
4. Content restrictions: you can restrict the users who can view/edit a page and its descendants.

That's it. You can find all these in the documentation, just search for the keyword in the list above.

Oh, and there is no such thing as sub-space in Confluence.

[Marc - Devoteam]

Hi @Roli T 

@Aron Gombas _Midori_ has explained this extensive and how Confluence uses permissions

There is n option to nest spaces. A Space is a container on its own within Confluence