-
Suggestion
-
Resolution: Unresolved
-
19
-
16
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
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.
Thanks for your suggestions and 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.
Some of you have also shared concerns around data privacy legislations being enforced in Europe next year. We'd like to assure you that Atlassian is committed to data privacy. Read more about this in our blog.
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. We are excited to share that External Collaboration will be added to Confluence Premium in the coming months. We will open up a free beta program of the feature within the next quarter, and will provide updates here as soon as you're able to sign up.
Many thanks,
Confluence Product Management
- duplicates
-
CONFCLOUD-7837 People Directory and "controlled" privacy / configure access to People Directory depending on Group membership
- Closed
- incorporates
-
CONFCLOUD-35377 Restrict the pool of users that is provided in the autocomplete of mentions and shares
- Closed
- is duplicated by
-
CONFCLOUD-20421 After removing People Directory, user names are still searchable
- Closed
-
CONFCLOUD-25258 Allow to limit social features on a group-level - Confluence first steps towards real multi-tenancy capability ...?
- Closed
-
CONFCLOUD-25675 Ability to show only users that are members of confluence-users in the People Directory
- Closed
-
CONFCLOUD-26601 User Picker Should not Listed All Users
- Closed
-
CONFCLOUD-31154 User name should be masked in the HTML source code
- Closed
- is related to
-
CONFCLOUD-26600 Group Picker Should Not Listed All Groups
- Closed
-
CONFCLOUD-28592 Restrict access to personal pages and directory
- Gathering Interest
-
CONFSERVER-1882 Restricting access to user names and profiles
- Gathering Interest
- relates to
-
CONFCLOUD-7837 People Directory and "controlled" privacy / configure access to People Directory depending on Group membership
- Closed
-
JRACLOUD-7659 Limit user picker to members of certain groups / roles
- Closed
- is addressed by
-
ENT-1247 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...