• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 1.4
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Viewing permissions can be set per page

            [CONFSERVER-2697] Page Level Permissions

            jens added a comment -

            We introduced a new space-level-permission on pages which restrict who is allowed to set page-level-permissions.

            We will also provide an overview of pages were permissions have been set. It will list the user who set the permission and the group, if applicable, which has permission to the page.

            jens added a comment - We introduced a new space-level-permission on pages which restrict who is allowed to set page-level-permissions. We will also provide an overview of pages were permissions have been set. It will list the user who set the permission and the group, if applicable, which has permission to the page.

            Sulka Haro added a comment -

            I'm not concerned of the UI used to lock the pages, I'm concerned of how an admin will be able to check which pages have restricted access in a space and which groups have been used for those pages. We have a large user base with a large amount of groups and it'll be a matter of time before each space has page restrictions using multiple groups...

            Ideally you'd provide a preference to turn this feature for individual spaces and allow defining which groups can be used for each space (kind of like Jira's schemes). This would also provide a mechanism to control who can restrict access - if you don't belong to a group which can be used for restricting access, you can't set page level permissions.

            Sulka Haro added a comment - I'm not concerned of the UI used to lock the pages, I'm concerned of how an admin will be able to check which pages have restricted access in a space and which groups have been used for those pages. We have a large user base with a large amount of groups and it'll be a matter of time before each space has page restrictions using multiple groups... Ideally you'd provide a preference to turn this feature for individual spaces and allow defining which groups can be used for each space (kind of like Jira's schemes). This would also provide a mechanism to control who can restrict access - if you don't belong to a group which can be used for restricting access, you can't set page level permissions.

            jens added a comment -

            The UI will look similar to the current "lock pages" UI. You will be able to give view and edit permission either to a group you are a member of, or restrict this permission to yourself. This should be simple enough and won't be hard to administrate.

            jens added a comment - The UI will look similar to the current "lock pages" UI. You will be able to give view and edit permission either to a group you are a member of, or restrict this permission to yourself. This should be simple enough and won't be hard to administrate.

            Sulka Haro added a comment -

            When implementing this, please be extra careful to create UI solutions which make it very clear to users on who can see/edit each page. Even as it is, regular users have no way of knowing who can see each space which is problematic and if the next version of Confluence both makes it hard to check both space- and page-level access, it'll be an administrative nightmare.

            Sulka Haro added a comment - When implementing this, please be extra careful to create UI solutions which make it very clear to users on who can see/edit each page. Even as it is, regular users have no way of knowing who can see each space which is problematic and if the next version of Confluence both makes it hard to check both space- and page-level access, it'll be an administrative nightmare.

              jens@atlassian.com jens
              jens@atlassian.com jens
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: