-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Suggestion CONF-19116 was recently implemented which drastically impacted the way we utilize Confluence. Rather than hard coding what the people directory should display it would be appreciated if this "Can Use" filter be moved to an enable/disable option, or allow custom filtering.
Some examples on what this suggestion impacted for us:
Prior to this change, we would utilize the People Directory along with the User Profiles for Confluence Add-on to display a company directory (Based on Active Directory user directory settings) to our visitors. Our entire user staff does not have a need to have "can use" functionality for Confluence, so this change now limits what is displayed to our end users which is currently only a handful of users.
Prior to this change we would utilize ConfiForms with a "User" field definition in order for our IT/Management team to log events relating to company staff (Again, not all staff have/need "Can Use" functionality). Using this field type was a big benefit as it allowed us to tie into Active Directory to ensure names are typed correctly, as well as pulling in additional info if needed (Photos, e-mail addresses, phone #'s and etc). This change eliminated this functionality as not all users were displayed, so we had to change this to a text field which limits functionality.
- is caused by
-
CONFCLOUD-19116 Only show users with "can use" permission in People Directory
- Closed
- is related to
-
CONFCLOUD-59128 Confluence People Directory Should Not Display Add-on Users
- Closed
-
CONFSERVER-40958 Create an option to determine what People Directory should display
- Gathering Interest
- relates to
-
CONFCLOUD-41178 Add option to control whether unlicensed users are hidden
- Gathering Interest