Upcoming changes to Atlassian account profiles

What's changing?

  • We will be providing improved controls to manage profile visibility across Atlassian cloud products, so that your users can choose who sees their personal information.

  • As part of an effort to consolidate user profiles, we're phasing out usernames in favor of using full names and public names when users are searched for and referenced in Jira Cloud and Bitbucket Cloud.

  • We’re introducing the use of public names, in addition to full names. Public names will display on community-oriented Atlassian sites, such as Atlassian Community and jira.atlassian.com.

  • Apps that you or your users may have installed in Atlassian cloud products are being updated to protect your users' privacy.

How do the profile changes affect users?

From their Atlassian account profiles, users will be able to control who can see the information on their profile using new profile visibility settings. Because of this, their profile information may look different depending on who’s viewing it.

The profile visibility settings affect site administrators, too. However, email addresses will always be visible to site administrators.

Managed account users

For fields in their profiles, users with managed accounts will be able to choose one of the following visibility settings:

  • Anyone - The information in this field is visible to anyone who can view their content. Depending on the product’s or site’s settings, this may include people outside of their organization. This information is also accessible by apps installed in Atlassian cloud products.

  • The name of their organization - The information in this field is only visible to other users managed by their organization.

  • Only you - The information in this field is only visible to the user.

When we release this change, we’ll set the visibility of full names and job titles to Anyone in both existing and new managed users' profile.

Unmanaged accounts users

For their profile photos, locations, local times, and email addresses, users with unmanaged accounts will be able to choose one of the following visibility settings:

  • Anyone - The information in this field is visible to anyone who can view their content, and it is accessible by apps installed in Atlassian cloud products.

  • Only you - The information in this field is only visible to the user.

Full names of users with unmanaged accounts will always be visible to Anyone. They’ll also have public names, which will display on community-oriented Atlassian sites.

When we release this change, we’ll set the visibility of fields in both existing and new unmanaged users' profiles to Anyone, except for email addresses.

What are public names?

We’re introducing the use of public names, in addition to full names. Public names will always display on community-oriented Atlassian sites, such as Atlassian Community and jira.atlassian.com.

Managed users will be able to restrict the visibility of their full names to their organization. When they do so, their public names will display to people outside their organization.

Users will be able use full names and public names to find other users, for example, when they mention other users or assign issues to them.

How do the profile changes affect apps installed in Atlassian cloud products?

Admins and users can install apps in Atlassian cloud products, for example, from Atlassian Marketplace. We’re limiting the profile information that apps can access. Because of this, you may notice some apps not working as expected:

  • Some apps haven’t been updated and may show “user not found” messages.
  • Others may stop working because they were relying on profile information that is no longer available to them.

Which profile information will apps be able to access?

  • Any personal information users set as Anyone will be available for apps to use. For example, apps will be able to access this information, store it, and show it to other users.

  • Users' local times and locations will always be available to apps, regardless of their visibility settings. This lets apps customize their experiences.

  • Users' email addresses will be available to some apps that have been approved by Atlassian. Note that if a user chooses to set their email address to Anyone, then any installed apps will be able to use it.

  • When users install apps, the apps will request that they consent to share their profile information with the apps. If they consent, the apps will have access to all of their profile information. This is not applicable to admins.

Which apps will be able to access email addresses?

There are some apps that require email addresses to work properly. To be given access to email addresses, these apps have to pass a legal review with Atlassian.

Before admins install any apps that have been approved to access email addresses, they’ll see a new action, View email addresses of users, on the installation consent screen.

Why is Atlassian making these changes?

To give your users more control over who sees their personal information and to protect their privacy.

What do you need to do?

You don't need to do anything. We’ll introduce the changes in the background.

When will this happen?

In the coming weeks, we’ll begin introducing profile visibility controls, as well as phasing in the use of public name on community-oriented Atlassian sites. We’ve already begun phasing out usernames from the products.

Powered by Confluence and Scroll Viewport.