Global permissions apply to the entire Confluence system. All content in Confluence is organised in spaces which can be used to cluster related information, for example, a team or a department can have their own space. Within spaces, there are pages which can be organised in hierarchies. As a space adminstrator, you may change the permissions for an entire space which are then imposed on all pages in that space. On a lower level, it is possible to define permissions for individual pages or page trees in a fine grained-manner.
Confluence has an hierarchical approach to access rihgts management and provides a fine grained permissions management at system level. These global permissions apply to the entire system and are inherited by all spaces, pages and child pages. They can then be overwritten at the space- and page-level.
A standard user will very rarely be confronted with system-level permissions. Please refer to Atlassian's online documentation of global permissions for more detailed information.
Users with appropriate permissions can create and configure their own spaces. Usually, this is done by space administrators who also later on will be able to administer the space persmissions.
Space administrators can manage permissions for spaces. System administrators can also manage permissions for spaces, including adding or removing space administrator permissions for a space. Have a look at the permissions of an example Confluence space.
Please refer to Atlassian's detailed online documentation on Assigning Space Permissions for more information on configuring space permissions in Confluence. Within spaces, it is possible to configure permissions for individual pages.
As a user, you can recognise restricted pages as they will be flagged with a little lock symbol.
Any user with the appropriate permissions can restrict a page for specific users or groups. Have a look at the video to learn how this works.
Confluence allows to apply restrictions separately for viewing and for editing of the page. Page restrictions are also valid for all child pages, this means that all child pages of a page will inherit the page restrictions of their parent page. In case a page has many child pages, this can cause that changing permissions on the parent page takes some time to process.
Users visiting a restricted page without appropriate permissions (e.g. via an e-mail link) may request access.
The page editors can then grant access to that user.