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

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



    • Feedback Policy:
      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.
    • PM Value:
    • Support reference count:
    • UIS:


      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



              sashac Aleksandar Cvetkovic
              Aaron Bauman, aaron morton, Adam Barnes, Admin Fernbach, Administrator, Agile Philosopher , Alan Wu, Albert Wu, Aldo Cauchi Savona, Aleksandar Cvetkovic, Alexander Kantz, Alexander Wegener, Alex Baru, Alexey Chernysh, André, Andre van der Elst, Andrew Hainsworth, Anthony Hill, Ashraf Eid, Ashton Treadway, Asim Thakker, Attila Zs, Audra Eng [Atlassian], Bastian Baumeister, Benjamin Wolf, Bernd Rinn, Bill Arconati, Bill Bailey, bint_IT, Blake Burdeen [HTTP Factory], Bridget, CarlL, Christian Stenger, Christopher Owen [Atlassian], Clay Monkus, Connor McCarty, Craig Smallman, Darren Martz, David A, David Bullock, Denise Kramer, Dewayne Lavelle, Dionne White, Dominik Oriet, Don Son, eddie borjas, Eirik Midttun, Elizabeth, Federico Valori, florian lenhard, foryouandyourcustomers, Frances Cohen, François Nonnenmacher, François Nonnenmacher, George Williams, Gerhard Alfanz, Haafiz Dossa, Hans-Peter Geier, Hans Petter Myrlie-Bjørn, Helen Newham, Helge Schroeter, Iain Rough, Igor Rodrigues, Jacob Dorman, Jacques Verryn, james@marnet.vn, Jens Wüstefeld, Jim Pitts, John Masson, Jon Marks, Jono Hill, Juha Krapinoja, Julie Yatchak, Kaspar Lüthi, Kiki Strauss, Koen Koppens, Korbinian Hackl, Kristine Coco, Larry Guest, Laurent Di Pasquale, Lisa Dyer, Lukas Kolbe, Maciej Kola, Marc Berger, Marcel Hungerbühler, Mari Car, Martin Kottisse, Martin Margesin, Matin Schiemann, Matt, Matthew Daize, Matthew Walker, Matthias Jupe, Matt Ryall, Mauro Badii, Maximilian Boos, Maximilian Ewert, Max Lynam, Michael D., Michael Krause, Michael Pfister, Mikhail Ershov, Mitrol, office account, Paulo da Silva, Planon, Preston Marshall, Ramon Roth, Raphael Joss, Ray Lum, Renee Crowley, Ric gamble, Robert Samuel White, rob kearey, Roel Croonenberghs, Roger Rooney, Ross Westerbur, Roy Truelove, Ryan Chase, Sarah Bär, Scott Herdman, Sean Au, Sean Williams, Sebastian Mehl, sidionA, Stephan Eisvogel, Stephen Sykes, Steve Pretzel, Steve White, Sung Park, Sylvain Gourvil, Thorleif Wiik, Tim Moore [Atlassian], TM Admin, Todd Simmons, Tom Davies, Tran Le, Trey Titone, Udo Bange, Víctor Márquez, Vijaysinh Patil, Wolfram Schoeb, Xavier Vaucois
              Last Touched By:
              SET Analytics Bot
              623 Vote for this issue
              422 Start watching this issue


                Last commented:
                18 weeks, 1 day ago
                PM Reviewed: