Upcoming changes to visibility of Atlassian Teams in organizations with original user management

[#1]

Hi Community folks 👋

I’m April, a product manager on Atlassian Teams (Teams). I’m sharing some upcoming changes that may affect who can view and use what Teams in your organization.

If you’re an organization admin, please read on.

What’s changing?

Your organization is either in:

1. Centralized user management - your users and groups are managed centrally across the organization in admin.atlassian.com.

2. Original user management - your users and groups are managed on the site level within products in admin.atlassian.com

If your organization is in (2) original user management, we’re making improvements the overall Teams and Groups experience by ensuring both groups and teams are visible to the same set of users.

What does this mean for me?

From 15 Jul 2025, if your organization:

• Doesn’t use Atlassian Teams yet

• Uses Atlassian Teams but only has 1 site

Then you Teams will be visible in the site that the Team was created in. For example, if your Team was created in vitafleet.atlassian.net:

• only users in vitafleet.atlassian.net will be able to see and use the team

This matches the visibility of your groups i.e. you groups are only visible to users within the same site.

This shouldn’t affect your day-to-day work, but if you choose to start using Teams, they will only be visible to users in the site that has been created in.

Please read this page for more information about the visibility of Teams across your organization and sites.

Why are we making this change?

This change makes it easier and more consistent to manage who can see and access groups and teams in the future, particularly as we intend to introduce Teams in permissions.

I don’t want my Teams to be seen by all users in the organization but my org doesn't match the criteria above. Can I please only show Teams to users within a respective site?

If your organization is:

• In original user management

• Has multiple sites

• Using Atlassian Teams

Then you may benefit from us limiting the visibility of your Teams to users within the site the Team was created in rather than the entire organization. Some benefits include:

1. When selecting or using Teams, the selection will be limited to Teams in a site only and not across the organization

2. Currently, changes to Teams in sandbox sites affect production sites - this will allow you to have distinct copies of Teams.

We have an incoming migration planned for this, but if you’re interested in these benefits today, please fill out Google form and we will be in touch if your organization is eligible.

Please don't hesitate to ask any questions, please do mention me if you do so I get a notification!

[Trudy Claspill]

I'm glad to see this change!

I know this was a huge issue for an Enterprise client I worked for that had dozens of cloud sites, generated from migrating dozens of independent business units that each had their own Data Center products. There were challenges with multiple business units using the same names for Teams, and that causing confusion when they all migrated to Cloud.