Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-1882

Restricting access to user names and profiles

    XMLWordPrintable

    Details

    • Support reference count:
      16
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      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.

      Atlassian Status as of December 2017

      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. 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.

      Many thanks,
      Confluence Product Management

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jeff.kunkle@nearinfinity.com Jeff Kunkle
              Votes:
              391 Vote for this issue
              Watchers:
              286 Start watching this issue

                Dates

                Created:
                Updated: