Ability to create "Public to organization" team in a Division


In a division, it is today impossible to create a public team.
Is it planned to make this possible?

There are many use cases:

  • transparency on who does what and when
  • visibility of project portfolios that are in several teams (without having to add people in the teams, in order to keep the real team members, same for projects)
  • workflow libraries
  • templates, wikis, …


Hi @Julien_RENAUD,

I don’t believe this is possible and I think in a lot of cases it would create issues as anyone could freely join this public team automatically bumping the number of paid seats in this division. The main reason why division’s team are private is to keep control of paid seats :slight_smile:

1 Like

Ah, fantastic point @Marie_OoO! Yeah… I think with a Division it just requires an extra step of Team management. With the help of @Bastien_Siebman’s Asana Overview and Asana Global Portfolio & Workload it is a tolerable effort.

Who are “anyone”?
I thought a division was a kind of small org inside an org, with its own team and own billing. And you could have several teams inside a division. Am I wrong ?

Are “paid seats” the users with an email corresponding to the division email domain?

@Julien_RENAUD you are not wrong. Anyone = others that are NOT part of the Division yet share the same domain of the org. Even though Teams are in a Division, they can still seen by users under the same org domain that are NOT a license user under the Division…and vice versa. Therefore, since any user under the same domain can see Teams inside the Division, if public, it would increase the licensed seats under the domain once those users join.

Paid seats in a Division are the unique count of users across all Teams within the Division. If I have a Division made up of 5 Teams with 5 unique users in each, then I have 25 paid seats. If one of the users from one Team under the Division joins another Team under the Division, you still have only 25 seats. If a user on a Team outside of the Division were to join a team inside the Division and they aren’t already a part of any of the Teams under the Division, that user takes up a new seat. There lies the issue with controlling the paid seats under a Division if some Teams were to be Public (where anyone and everyone could join without approval).


I didn’t know that, and it explains everything.
So just to confirm, if you click “Browse more teams” at the bottom of the left panel, then you see all the teams that don’t even belong to your division?

1 Like

CORRECT! :raised_hands:


@Julien_RENAUD do I have your blessing to change this topic to #tipsandtricks? I think @Marie_OoO’s point makes it an ill-advised #productfeedback. Wouldn’t you agree?

If you don’t agree… I am sending you the bill for the unwelcomed, extra paid seats! :rofl:


Thank you to both of you, it’s much clearer now :+1:


Always welcome, @Julien_RENAUD. I am very happy that it is clear that I can forward invoices to you! :wink:

1 Like

You’re my “Division” specialist so I’m afraid the bill will go up again soon :scream:


Thanks @Jerod_Hillard for your help! I am happy to see I am making your life tolerable :rofl:

1 Like

This data model is a major problem for us, has prevented other parts of our organization from adopting Asana. Our division is a small department in a university. Every client we work with shares our email suffix and so for Asana’s purpose is considered part of our organization. This extends to every person who has ever taken a course at the university - all students and alumni, tens of thousands of people.

As a result for collaboration purposes, Asana has become an anti-collaboration tool beyond our internal task management and we have to have other systems for dealing with our clients, stakeholders, and for transparency. I’m sorry to say it’s only a matter of time before one of these other systems replaces Asana and we, unfortunately, have to advise against other units adopting it despite loving the UX and other functionality.

If anyone knows of a way we can work around this, I’d be very grateful for any tips. Asana is a fantastic tool, it’s just clearly not built for small groups inside large organizations. What would be ideal is some kind of limited access similar to “guest” passes.