Managed Teams are now available for Premium and Enterprise customers!

[#1]

Hi everyone 👋

My name is April, I'm a product manager working on Atlassian Teams.

I'm excited to announce that we're publicly releasing our new Team configuration called Managed Teams today. 

Currently, there’s only one type of team, that can either be invite-only or open to all. From today onwards, you should be able to see Managed Teams.

All eligible customers will have access to Managed Teams by the end of March. 

**For those in the EAP, you will not experience any changes. 

This feature will be available for organizations with at least one Premium or Enterprise plan for Jira Cloud, Confluence Cloud, Loom, or Compass.

What are Managed Teams?

Managed Teams are teams that have been connected to a group, which becomes the source of truth for membership in that team. You can connect either an externally managed group or a local Atlassian group.

• Managed Teams can only be created and deleted by organization admins in Atlassian Administration

• The connected group acts as the source of truth membership, meaning:

  • Any membership changes to the group will be automatically reflected in the connected team

  • Team name will change to match the group, but organization admins can rename it on the team profile.

• Since Managed Teams can only be changed by organization admins, they are given a  verified indicator when shown across apps.

Why did we build this?

Your feedback was a big factor in this, as we heard from multiple organizations that were encountering these challenges:

1. Having to manually create large Teams despite team structure existing in an external source already.

2. Having to manually update Teams, which is unsustainable due to frequent reorganizations and employees joining or leaving.

3. The risk of end users inadvertently connecting an 'unofficial’ Team to work used in critical reporting workflows.

Managed Teams are kept up-to-date with the connected group and remove the friction in keeping teams accurate and updated.

🔨 How to create a Managed Team

** The following can only be done if you’re an organization admin.

To create a managed team, you can either connect a group to an existing team or create a new one to connect to. The group you connect a team to can either be a SCIM-synced group or a local group.

1. Find the group you want to connect in the Groups directory in Atlassian Admin.

2. On the group’s profile page, find the Create team or Connect team button near the members list.

   1. For teams connected to SCIM-synced groups, team membership will mirror the group’s membership that’s pulled from an external source.

   2. For teams connected to local groups, team membership mirrors the connected group’s.

🤝 Incorporate Managed Teams into your work

Associate your work with Managed Teams: Teams indicated by a  are Managed Teams that have been ‘verified’ by an admin.

View the Managed Team and their work: End users and org admins can view Managed Teams and their activity in their own page indicated by  .

👓 Oversee your Managed Teams

Keep your Managed Team secure: Managed Teams cannot be created, deleted, or managed by end users. It mirrors the metadata in the group - manage the membership in Atlassian Administration through the group.

📝 View all Team activity in the audit log: View when your Teams are created, deleted, or edited in the audit log. This can be viewed for user managed Teams too if you have access to Atlassian Guard.

Please comment below if you have any questions and I will endeavour to get back to you as soon as possible. 

Cheers,

April

[Filip Labarque]

This sounds great. Will a managed team also prevent the creation of teams with the same name?

[Christopher Franzke]

It is possible to add a Team to an Asset Object as attribute for automatically Team assignments? We are missing this Feature very hard :)

[Haddon Fisher]

Hi April! I'd be curious if you could share Atlassian's long-term vision for "Teams".

With this change, the difference between a group and a managed team is (as far as I can tell) just where you can use them. If this is true, what is the intention of having two distinct and somewhat non-overlapping solutions to the same problem?

[Yatish Madhav]

Thanks @April Chi  and @Atlassian!

This is great! I am looking forward to this change being rolled out to us!

I agree with @Haddon Fisher - there should be a good distinction between the 2 ... i would almost assume groups are only for org admin permissions while teams allows for some level of additional granular permissions down the road but again that would be something configurable on the same solution again.

When can I expect this to be rolled out on our instance? I thought I commented here yesterday but it didnt post - i searched our "Product updates" and I only see this