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! 
2 Likes
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.
15 Likes
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.
4 Likes
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!
4 Likes
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.
Thanks!
2 Likes
Yes, this is very annoying, along with a âFirst Teamâ being created for every new user.
1 Like
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.
3 Likes
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.
3 Likes
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!
2 Likes
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!
3 Likes
Thanks. Hope we can get the lock feature still added in a future update.
3 Likes
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
need ability NOW to prevent users from creating teams. enough! Users creating teams is more work about work, and that is the opposite of what Asana is about.
We canât even delete accidentally created teams since the workspace owner is not the team admin.
Fond Regards.
1 Like
I just started the enterprise and honestly itâs already a big issue. The biggest reason we chose asana is because of the visibility feature but if members are allowed to 1. create accounts and automatically join our workspace without us being able to approve and then 2. Create their own teams and exclude the admins from it, then weâre essentially paying a program from people to build their own siloed space. This is exactly what we are trying to fix
2 Likes
@Emily_Roman Any updates on this? We are looking to reorganise our Asana use but this is a big blocker. At an org of a certain size, you just need the ability to control who can do what. This, and the option for super admins to see all projects are the two most important features for me. The effort required to delete old stale teams right now is astronomical and not at all efficient as Asana is supposed to be. At least hide the stupid plus symbol next to the Teams section in the sidebar and make it harder to create teams in the first place. Or add an approval step.
2 Likes