Migration state for centralized user management customers
Learn how Teams features are affected in a hybrid state and explore options to align your team visibility with your org setup.
Teams app customers in hybrid migration state
An overview on migration
This migration is only relevant to organizations using “original” user management (not “centralized”) whose Atlassian Teams are in a hybrid migration state.
Details on determining “original” versus “centralized” user management
How to know if your organization is included
If you are an organization admin, you will have received or seen one of the following:
An email notification regarding ‘Atlassian teams’
An in-product notification about ‘Atlassian teams’ in your Atlassian inbox
If you see any of these notifications, your organization is in this state.
Alternate migration
There are a small number of customers using the centralized user management who requested to opt in to Site Scoped Teams and are having a different migration applied. These customers can read more about the migration state. You will have received an email if you are in this state.
We recently aligned Atlassian Teams with group-level visibility to simplify administration and access controls. Read the full update
Most customers have already completed this migration. Your organization is currently in a hybrid migration state: Groups are scoped to a specific site, but Teams remain visible at the organization level.
Resolve a hybrid migration state for Atlassian Teams
Explore your options to move your organization out of a hybrid migration state for Atlassian Teams.
Understand Teams feature limitations in a hybrid state
Learn how a hybrid migration state limits new Atlassian Teams features and affects user visibility.
Was this helpful?
Still need help?
The Atlassian Community is here for you.