-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
4
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? 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.
- relates to
-
- Gathering Interest
[CONFSERVER-27622] Hide specific users (like bots) from People Directory without deactivating them
+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.
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.
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.
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. 
Deleted Account (Inactive)
added a comment - 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.
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.
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. 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
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center