-
Suggestion
-
Resolution: Unresolved
-
None
-
71
-
86
-
NOTE: This suggestion is for Confluence Data Center. Using Confluence Cloud? See the corresponding suggestion.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this ticket and weighing it up against our other opportunities, we have decided to transition it to 'Gathering interest' as we don't have plans to work on this in the near term.
Please continue to vote and watch this suggestion if it is important to your team, as we regularly review highly ranked tickets as potential roadmap items.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
In addition to sharing information within my company, we would like to use Confluence for sharing certain information with our customers and clients, and have it host our public website. The one thing that is holding us back from doing this is the inability to restrict who can see a user's profile. Profiles can even be viewed by anonymous users and to my knowledge there is no way to create a named user account without also creating a profile. Someone please correct me if I'm wrong. In our case, many of our clients are also direct competitors, and the last thing we want to do is give them a list of all our employees. The same concern also applies to the names at the top of each page, on the dashboard, in the search results, etc., that tell you who last changed the page and at what date and time.
I tried to come up with couple of ideas about how restriction of user profiles and user names might work. My preferred solution by far is number one but it may also be the most difficult to implement.
1. A user is only allowed to see the name and profile of another user if they are in the same group. (at least one group, not all)
2. Allow a global administrative option for enabling/disabling user names and profiles.
3. Allow each user to decide whether their name and/or profile should be viewable.
I think that this feature would be useful for many people, although I don't want to speak for other customers. Having such a feature would certainly allow the product to penetrate many more areas of my company.
Thank you for your continued feedback on this issue. We do agree that restricting access to user names and profiles could be valuable for users, particularly in an externally-facing Confluence environments.
The use cases stemming from external collaboration do touch quite a number of features in the product including user profiles, people directory, mentions, shares, comments 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.
Note that you can restrict Confluence so that anonymous users cannot view user profiles (See our documentation).
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.
Best,
Jenny - Confluence Product Manager
- duplicates
-
CONFSERVER-1134 Permissions for user profiles
- Closed
-
CONFSERVER-7837 People Directory and "controlled" privacy / configure access to People Directory depending on Group membership
- Gathering Interest
- incorporates
-
CONFSERVER-35377 Restrict the pool of users that is provided in the autocomplete of mentions and shares
- Closed
- is duplicated by
-
CONFSERVER-20421 After removing People Directory, user names are still searchable
- Closed
-
CONFSERVER-25258 Allow to limit social features on a group-level - Confluence first steps towards real multi-tenancy capability ...?
- Closed
-
CONFSERVER-25675 Ability to show only users that are members of confluence-users in the People Directory
- Closed
-
CONFSERVER-26601 User Picker Should not Listed All Users
- Closed
-
CONFSERVER-28592 Restrict access to personal pages and directory
- Closed
-
CONFSERVER-31154 User name should be masked in the HTML source code
- Closed
-
CONFSERVER-36061 Restricting profile viewing from @mention in Confluence similar to how JIRA handles it with permissions
- Closed
-
CONFSERVER-46201 Extend Confluence Mentions Plugin to allow limiting the mentioned users
- Closed
- is related to
-
CONFSERVER-13276 Restrict anonymous users from viewing user profiles.
- Closed
-
CONFSERVER-26895 Confluence creates a USERINFO for all users from JIRA
- Closed
-
CONFSERVER-10719 Recently Updated List has users that aren't in current group
- Closed
-
CONFSERVER-26600 Group Picker Should Not Listed All Groups
- Closed
-
CONFSERVER-32838 Ability to Customise People Directory
- Closed
- relates to
-
JRASERVER-7659 Limit user picker to members of certain groups / roles
- Closed
-
JRASERVER-66161 As an admin, allow me configuring what user's information is shared between users
- Closed
-
CONFCLOUD-1882 Restricting access to user names and profiles
- Gathering Interest
-
CONFSERVER-7837 People Directory and "controlled" privacy / configure access to People Directory depending on Group membership
- Gathering Interest
-
SSE-191 Loading...
-
ENT-1657 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...