NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Requirement:
Depending on group membership users may (or may not) see users in their own or in other groups in the People Directory.
Scenario example:
- Internal people should be able to see all users (from their department and/or project group) as well as all customers that they are responsible for / ideally grouped per company/department/...
- External users (customers) from company XYZ should be able to see (some) internal users (i.e. those responsible for their project), in addition all users from their own organization (members in the group XYZ) and possibly some users from another company that is utilizing the same product.
Above could be solved by smart grouping of people, provided that the access to the People Directory is "better" configurable.
Note: The "Shared Mode" setting in the General Configuration does not solve the issue - this is an all-or-nothing approach, it would be highly desirable to have a fine-grained controlled access to the People Directory in one of the future Confluence releases.
Atlassian Status as of October 2022 |
---|
Hi All, We have completed rolling out the Single-Space Guest experience in Beta to all our Standard, Premium and Enterprise customers. You can bring contractors, vendors, and partners securely into Confluence! Organization admins will be able invite up to 5 free guests for each paid user on their site! Each guest is allowed access to one space at a time, and they will not have access to the People Directory. Read more on our Atlassian Community post and our support articles: article 1: how to get set up and article 2: What guests can and can't do. Happy collaborating, Nidhi Product Manager, Confluence |
Thank you for your patience and being so vocal with regards to availability of this feature in Confluence Cloud. We acknowledge that many of you are looking to bring your customers and other external users into your Confluence site and therefore want tighter control over which users can browse the people directory.
I'm happy to share that we've put this suggestion on our roadmap and are planning to address it in the next 12 months.
We will keep you updated on the progress and timelines when the feature is going to be delivered.
Thanks again for your patience.
Best,
Hilary Dubin
Product Manager, Confluence Cloud|
- is duplicated by
-
CONFCLOUD-12842 Disabling the People Directory section from the Browse menu
- Closed
-
CONFCLOUD-26564 Limit user search ability
- Closed
-
CONFCLOUD-36964 Ability to Hide the People Directory from certain Users or Groups
- Closed
-
CONFCLOUD-40485 Restrict access to People Directory for certain user groups
- Closed
-
CONFCLOUD-74694 Guest or External Users of a Confluence site shouldn't view the details of other site users within the same organization
- Closed
-
CONFCLOUD-1882 Restricting access to user names and profiles
- Gathering Interest
- is incorporated by
-
JRACLOUD-60623 JIRA users should not see Confluence users' Profile Picture update in Activity Stream
- Closed
- is related to
-
CONFCLOUD-26564 Limit user search ability
- Closed
-
JRACLOUD-7776 When adding watchers, the user-picker dialog should only show users who have access to the project.
- Closed
-
CONFCLOUD-1882 Restricting access to user names and profiles
- Gathering Interest
-
CONFCLOUD-29961 Limit @mentions and share feature to specific groups
- Gathering Interest
-
CONFSERVER-7837 People Directory and "controlled" privacy / configure access to People Directory depending on Group membership
- Gathering Interest
- relates to
-
CONFCLOUD-12842 Disabling the People Directory section from the Browse menu
- Closed
-
CONFCLOUD-13728 Create an option to hide users that are not allowed to have a personal page from the people directory
- Gathering Interest
-
CONFCLOUD-28592 Restrict access to personal pages and directory
- Gathering Interest
-
CONFCLOUD-46420 User email visibility set by groups/space
- Gathering Interest
- 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...