Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-28592

Restrict access to personal pages and directory

XMLWordPrintable

    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      We need to restrict access to personal pages and the directory. At present, there doesn't seem to be any way to do this.

      We have some guest accounts that we want to share a particular space with but unfortunately, we can not do that as all of the content in personal spaces and our directory are accessible to a regular user.

      We also tried to remove these users from our "user" group but that invites nothing but disaster as nothing will work.

            [CONFSERVER-28592] Restrict access to personal pages and directory

            Adam Barnes (Inactive) added a comment -

            This suggestion as far as the description and comments describe is a duplicate of CONFSERVER-1882: Restricting access to user names and profiles and CONFSERVER-7837: People Directory and "controlled" privacy / configure access to People Directory depending on Group membership.
            Please vote on the linked issues.

            Cheers,
            Adam - Confluence PM

            Adam Barnes (Inactive) added a comment - This suggestion as far as the description and comments describe is a duplicate of CONFSERVER-1882: Restricting access to user names and profiles and CONFSERVER-7837: People Directory and "controlled" privacy / configure access to People Directory depending on Group membership . Please vote on the linked issues. Cheers, Adam - Confluence PM

            Maximilian Boos added a comment -

            We struggled with the issue to collaborate with externals (guests) in our instance. The confluence space restriction does not fit our requirements because we don’t want the externals to see each other and all of our internal users.
            On the other hand we don`t want to miss confluence features like the user search, mentions and so on.
            So we developed the "Space Privacy- Extranet for Confluence" add-on. It allows you to create isolated extranet spaces. In these spaces, assigned users keep to themselves – just like in meeting rooms. That is, they do not have access to other information from fellow user data. 

            Maximilian Boos added a comment - We struggled with the issue to collaborate with externals (guests) in our instance. The confluence space restriction does not fit our requirements because we don’t want the externals to see each other and all of our internal users. On the other hand we don`t want to miss confluence features like the user search, mentions and so on. So we developed the " Space Privacy- Extranet for Confluence " add-on. It allows you to create isolated extranet spaces. In these spaces, assigned users keep to themselves – just like in meeting rooms. That is, they do not have access to other information from fellow user data. 

            Richard Atkins added a comment -

            This looks like it has come overlap with https://jira.atlassian.com/browse/CONF-7837, but that issue doesn't mention locking down the space directory or making it easier to restrict access to personal spaces.

            There is currently no way to restrict access to existing personal spaces through the global administration console. The owner user, or an administrator, would have to visit each space, browse to its administration screen, and change its permissions.

            However, the settings in the Space Permissions global administration console apply to all new personal spaces as well as global spaces. If a user selects Private when they create a space, then only they have access to their new space. Otherwise, their space inherits the current space permissions defaults.

            If all of this sounds like too much hassle to worry about, you can disable the use of personal spaces for all users and groups through the Global Permissions administration console.

            Richard Atkins added a comment - This looks like it has come overlap with https://jira.atlassian.com/browse/CONF-7837 , but that issue doesn't mention locking down the space directory or making it easier to restrict access to personal spaces. There is currently no way to restrict access to existing personal spaces through the global administration console. The owner user, or an administrator, would have to visit each space, browse to its administration screen, and change its permissions. However, the settings in the Space Permissions global administration console apply to all new personal spaces as well as global spaces. If a user selects Private when they create a space, then only they have access to their new space. Otherwise, their space inherits the current space permissions defaults. If all of this sounds like too much hassle to worry about, you can disable the use of personal spaces for all users and groups through the Global Permissions administration console.

              Unassigned Unassigned
              d5411951e028 Brian Vetter
              Votes:
              17 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: