Understanding verification for teams
Verified teams are designated by organization admins as accurate or reliable membership and details. There are different ways a team can become verified, but it often has to do with limiting how the team is changed and who can make changes to the team. Currently, teams become verified by:
Having a team type that’s verified by an admin
Verified teams have the following attributes:
They can only be created and deleted by organization admins in Atlassian Administration.
If connected to an external source, membership is synced between the source and Atlassian and membership can only be changed in the external source.
Verified teams have the blue, verified checkmark in most places they’re shown or mentioned.
What happened with managed teams?
In a previous release, we designated all group and HRIS-synced teams as “Managed teams” to distinguish them from normal, member-managed teams. While the concepts of “managed teams” and team verification still exist, we’ve moved away from “managed teams” terminology with the release of the team types system to give organization admins a more meaningful way to distinguish between different sets of teams.
Was this helpful?