Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-9470

Allow administrators to change users' full name (SSO)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None

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

      Atlassian Update – 28 February 2019

      Hi everyone,

      Thanks for voting and commenting on this issue. I wanted to share a short update – this request is not on our roadmap at this time. While we understand the desire to have consistent naming schemes within individual Jira or Confluence Cloud instance, users' full names are considering personally identifiable informations and are subject to the control of the end user. In the case that a user is a managed account of their organization (achieved via the domain claim process), the users' organization admin can also modify their public name. This is described in our Privacy Policy.

      In cases where there is a strong requirement for control within a single Jira or Confluence Cloud instance, we recommend creating accounts for external users under a domain that is controlled by the company that owns the instance.

      We appreciate your feedback. It's key to helping us understand how we can continue improving your experience with our products. 

      Kind regards,
      Dave Meyer
      Atlassian Product Management

      Problem Definition

      Administrators of instances using Atlassian Account are requesting the option to edit users' full name even if their domain has not been claimed. This is important in situations that a user creates an Atlassian ID with a domain not owned by the administrator, and sets his full name to something not allowed on the instance or that will make difficult to search for that user. For example, it is possible to set the full name to the same as an existing user of the instance, which is unacceptable.

      Suggested Solution

      Allow site administrators to edit users' full name again. Another option would be to create a policy on the information not editable by the administrator. For example, one that prevents the user from setting his full name if it is already being used on the instance.

      Workaround

      A workaround would be to suggest that the user updates his full name, which may not be possible because relies on the users' cooperation.

              Unassigned Unassigned
              bandreeti Bernardo Andreeti
              Votes:
              55 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated:
                Resolved: