Org admins can now rename Managed Teams in team profile pages

[#1]

Hi everyone 👋

My name is April, I’m a product manager building Atlassian Team features.

Earlier in the year, we released Managed Teams. These 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.

Next week onwards, you can rename your Managed Teams by going directly to the team profile.

From August onwards, you will be able to rename Managed Teams in Atlassian Administration itself when connecting the group. We will make another post when this is available.

Why we built this

Your feedback was a big factor in this, we heard from many organizations that your group names weren’t friendly to end users.

How to rename your managed teams

Renaming your Managed Team is the same as renaming any other team.

1. Visit the team profile of your Managed Team.

2. To rename the team:

   a) Click into team name and rename the team inline.
   b) Click into the ‘team settings’ dialog and rename the team in the ‘team name’ field.

3. In Atlassian Administration, you will see that your team has been renamed successfully.

Please feel free to comment and leave any feedback!

[Yatish Madhav]

Great - thanks for this @April Chi 

So, this means that we can have Teams and user groups with different names. I think in our use cases, there is no need for this just yet.

Perhaps, if you can share ideas or use cases where this would make sense or on reasons this was needed, that may also help provoke some thoughts in the community (and for me personally :) ) too?

Thank you again

Yatish

[Jordi Garcia]

@Yatish Madhav, this was a really important update for us.

We use SCIM to sync groups from our identity provider (Okta) into Atlassian via Atlassian Guard. These synced groups—known as Atlassian Groups—inherit their names from Okta and couldn't be renamed within Atlassian.

For example, we have a group in Okta called `department-legal`, and when it's synced, the Atlassian Group is also named `department-legal`. That name is then automatically applied when the group is linked to an Atlassian Team—making the team name `department-legal`, which isn’t user-friendly or intuitive for our employees.

Our users are more familiar with the simpler team name `Legal`. But because the team name was locked to the group name, we couldn’t make that change.

This new ability to rename the team while keeping it connected to the managed group is a big improvement for usability. This might not have the same impact to all customers, but most enterprise companies might experience the same pain we do.

I also know Atlassian is working on a longer-term solution to allow Atlassian Groups to have different display names from their identity provider counterparts, tracked here: https://jira.atlassian.com/browse/ACCESS-800