Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-27622

Hide specific users (like bots) from People Directory without deactivating them

    • 1
    • 6
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      In Confluence 4.3.3, a new feature is introduced to filter out disabled/deactivated users from the People Directory. However, there is a need to hide specific users from People Directory without deactivating them.

            [CONFCLOUD-27622] Hide specific users (like bots) from People Directory without deactivating them

            CT CHANG added a comment -

            People Directory should excluded all the system users or users created by those addOns/Plugin.

            CT CHANG added a comment - People Directory should excluded all the system users or users created by those addOns/Plugin.

            Brian Hill added a comment -

            +1 from me. There are a range of service accounts that I need to mask within confluence instances for clients - not all clients are strong on AD management, so there are times when having the ability to mask a result set would be really useful, especially via both a ruleset and quick UI action.

            Brian Hill added a comment - +1 from me. There are a range of service accounts that I need to mask within confluence instances for clients - not all clients are strong on AD management, so there are times when having the ability to mask a result set would be really useful, especially via both a ruleset and quick UI action.

            Ed Snow added a comment -

            We're a contract engineering firm and want to use jira/confluence with our clients. The lack of control over visibility between clients is a big concern. This feature would help us isolate our clients.

            Ed Snow added a comment - We're a contract engineering firm and want to use jira/confluence with our clients. The lack of control over visibility between clients is a big concern. This feature would help us isolate our clients.

            Right now, for the ease of it, we maintain one user database in JIRA for both JIRA and Confluence. The problem is that Confluence is an internal tool, whereas JIRA is used as an external database. When syncing users, all users are carried over. This, in and of itself, is fine, but being able to hide them in the people directory - or restrict the People Directory to only show a certain user group, would be an amazing feature and would clean up the functionality nicely.

            Robert Swarts added a comment - Right now, for the ease of it, we maintain one user database in JIRA for both JIRA and Confluence. The problem is that Confluence is an internal tool, whereas JIRA is used as an external database. When syncing users, all users are carried over. This, in and of itself, is fine, but being able to hide them in the people directory - or restrict the People Directory to only show a certain user group, would be an amazing feature and would clean up the functionality nicely.

            This would indeed be valuable to hide service accounts - allowing the people directory to be neat and tidy.

            Deleted Account (Inactive) added a comment - This would indeed be valuable to hide service accounts - allowing the people directory to be neat and tidy.

            We also have service accounts that can access Confluence to create/update pages and the like, but do not want them to be in the people directory.

            Davin Studer added a comment - We also have service accounts that can access Confluence to create/update pages and the like, but do not want them to be in the people directory.

            I'm actually interested in this as well. We have shared/bot users in our Google Apps account, departed employees, and a number of other situations where there are Apps users that ought not be in the "People Directory".

            It seems like it should be possible to require a group membership to appear in the People directory. For Google Apps connected accounts, simply only showing members of the "users" group (or a admin-selectable group) would go a long way toward improving this problem.

            Kyle VanderBeek added a comment - I'm actually interested in this as well. We have shared/bot users in our Google Apps account, departed employees, and a number of other situations where there are Apps users that ought not be in the "People Directory". It seems like it should be possible to require a group membership to appear in the People directory. For Google Apps connected accounts, simply only showing members of the "users" group (or a admin-selectable group) would go a long way toward improving this problem.

            BillA added a comment -

            I see. Thanks for explaining. I've opened the ticket and updated the description. Thank you.

            BillA added a comment - I see. Thanks for explaining. I've opened the ticket and updated the description. Thank you.

            Hi Bill,

            I use JIRA Mobile Connect which creates a special user that can auto submit tickets from mobile clients. When I look at the public directory I can see that user (JIRA Connect User). Also sometimes I need clients to access Confluence. I don't want their names showing up in the public directory. In a nutshell there could be many reasons why we create users (for admin purposes, technical reasons etc.) But as a company we should have full control over which users are visible to the public.

            Cheers,

            Rom

            Romulo Velasquez added a comment - Hi Bill, I use JIRA Mobile Connect which creates a special user that can auto submit tickets from mobile clients. When I look at the public directory I can see that user (JIRA Connect User). Also sometimes I need clients to access Confluence. I don't want their names showing up in the public directory. In a nutshell there could be many reasons why we create users (for admin purposes, technical reasons etc.) But as a company we should have full control over which users are visible to the public. Cheers, Rom

            BillA added a comment -

            Hi Amalia and Romolo, can we get more reasoning behind needing to hide users from the people directory?

            BillA added a comment - Hi Amalia and Romolo, can we get more reasoning behind needing to hide users from the people directory?

              Unassigned Unassigned
              asanusi AmaliaA
              Votes:
              23 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: