Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-7837

People Directory and "controlled" privacy / configure access to People Directory depending on Group membership



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

      Depending on group membership users may (or may not) see users in their own or in other groups in the People Directory.

      Scenario example:

      • Internal people should be able to see all users (from their department and/or project group) as well as all customers that they are responsible for / ideally grouped per company/department/...
      • External users (customers) from company XYZ should be able to see (some) internal users (i.e. those responsible for their project), in addition all users from their own organization (members in the group XYZ) and possibly some users from another company that is utilizing the same product.

      Above could be solved by smart grouping of people, provided that the access to the People Directory is "better" configurable.

      Note: The "Shared Mode" setting in the General Configuration does not solve the issue - this is an all-or-nothing approach, it would be highly desirable to have a fine-grained controlled access to the People Directory in one of the future Confluence releases.

      Atlassian Update - December 2018

      Thank you for your continued feedback on this issue. We acknowledge that many of you are looking to bring your customers and other external users into your Confluence site and therefore want tighter control over which users can browse the people directory. 

      At this stage we do not have a way to control who can browse the people directory. If it is crucial for you to completely hide the people directory from all users, we have instructions on how to disable this in your self-hosted instance. We do know that the people directory is extremely useful and that you still want to make it available for some users, like your internal employees. 

      The use cases stemming from external collaboration do touch quite a number of features in the product, starting from the people directory and ranging through mentions, shares, comments, user profiles and search. In order to provide both a functional and watertight solution it is important to consider these various use cases, their impact on various features and the related front end and API implementations.

       This feature request does form part of a larger long term initiative from which we hope to provide a solution for this issue in the future. We will update the status of this issue once we have made further progress.

      Some of you have also shared concerns around data privacy and GDPR. We'd like to assure you that we’re continuing to take these requirements seriously. For more information on our latest GDPR updates to Confluence, see our 6.13 release notes

      Jenny - Confluence Product Manager


        1. 7837.jpg
          86 kB
        2. Capture.PNG
          20 kB

        Issue Links



              Unassigned Unassigned
              eb86238c4f4d Aleksandar Cvetkovic
              696 Vote for this issue
              465 Start watching this issue