Creating teams - administrator only

Should any category of user be able to create a team or is it just for administrators?

Hi @David_Louis_Puttick! Any Members can create a Team (How to Create, Join, and Manage teams in Asana | Product guide • Asana Product Guide), except Guests Members (Asana FAQs and common questions | Product Guide • Asana Product Guide). You don’t necessarily need to be Admin, you just need to be a Member of the Organization. Hope this helps! :slight_smile:


I realize this is an older issue, but would love the ability to lock down team creation to admins only. Our management team is spending quite a bit of time, cleaning up old/junk teams from the last couple of years, and I think it would help us keep things tidy if we could prevent standard users from making random & unnecessary additions.


Same for me. Especially since we have “official” teams built in Active Directory and synced to all our systems, including Asana, we don’t want people creating one-off teams that only live in Asana… that confuses everyone.

1 Like

We’re experiencing the same issue. Spending too much time maintaining the organization of our projects due to outdated or unnecessary teams that get created by those not responsible for the managing the organization of tasks. I would the ability to define our own users roles as it fits within our company.

Curious on this one as well, we are just about to implement Azure AD and wanted to know if we could lock down team creation so that people don’t stray outside of the defined team structure in AD.

Our organization has standards in place that state “only admins may create teams in Asana”, however this is not enough. The ability to lock down which type of user can create teams is needed.

Our organization permits teams which represent departments; however, some users create teams for committees or focus groups. There are times when a new user accidentally spins up a “[Name]'s First Team”.

Admins have to manually review for rogue teams, connect with the user, explain what they did, move projects, and delete the team. It is a maintenance that could be prevented if we had control over who can create teams.

Thanks! :slight_smile:

1 Like

Marie - wasn’t sure if you got notifications since the replies to this thread haven’t been directed to you specifically, but I was wondering if this could be looked at for a feature for organizations to be able to restrict this so that only Admins are able to create - it looks like there are a number of other users with the same request. It wouldn’t have to be restricted by default for all organizations but adding the ability to turn that restriction on would be great.

1 Like

Yes, this is very annoying, along with a “First Team” being created for every new user.

Today was the first time I actually saw where new users are being told to create a team. There is a checklist presented to new users on the homepage and a series of tasks within their My Tasks. One of these items is to “Create First Team”, which is why associates are constantly creating new teams when they are added to our organization. This is becoming a lot to keep up with and I hope to see this removed as well as the ability to restrict “members” from creating teams.


I would love to see something added in security for approval and/or creation of Teams. It would be great if you had the ability to limit this to Admins/Super Admins.


Hey @anon25809276,

I agree this can be useful for orgs.
I have found an existing feedback request thread and merged your post. Don‘t forget to upvote.

1 Like

I agree with many of the above users. The ability to limit which users have the ability to create teams is needed!


This would be very helpful for our company as well.

Hi everyone, and thanks for sharing feedback with us around the ability to lock team’s creation to Admins only. This feature is currently not available, but we have just launched a workaround that will hopefully bring some clarity.

We understand that administrators in large enterprise organizations strive to standardize and curate teams within Asana, making it essential to differentiate endorsed teams from the rest. Today, we have started rolling out Endorsed teams, designed to empower admins to clearly identify and promote selected teams for enhanced collaboration and easier team recognition.

In conjunction with this exciting feature, we’re introducing the ability to automatically set teams synced from popular identity providers such as Okta, Azure AD, and OneLogin as endorsed by default via a setting in the admin console. This integration provides seamless management and ensures endorsed teams align effortlessly with the organizational structure.

This feature is available to Admins of Enterprise Organizations.

I will keep this thread open and will keep you posted if we have any news about the ability to lock team creation to admins only. Let me know if you have any questions! :slight_smile:


Thanks. Hope we can get the lock feature still added in a future update.


This is an interesting feature, but it doesn’t solve the core problem. So long as anybody can create a team, they inevitably will. We are trying to keep things organized so we don’t end up with a “Client ABC” team and a “Client A.B.C.” team and a “Client ABC Inc” team. Yes, we can merge the teams later, but somebody has to realize the problem and fix it manually.

I can only guess this request goes against Asana’s ethos; otherwise it seems odd to add an entirely new feature rather than simply disable the add team button based on role. If true, perhaps the lock feature could be given to enterprise subscriptions only, or to those with SCIM group creation, etc.

1 Like