What I learned about divisions 😅

English Forum Community Tips Forum Leader tips
42

A new information discovered today.
In a division, a user can deprovision another user. This is not limited to the free teams that are in the free organization.

Users cannot remove members from an organization only when the paid plan is implemented on the entire organization.

43

Do you mean “an admin can deprovison…”? You don’t mean any old regular user can deprovision another user, do you?

44

Not only an admin, anyone can… :scream:

1 Like
45

This is good to know and a bit scary!

46

:wave: @Julien_RENAUD! Your example process for moving from a Premium org to a Premium team converting it to a division which can then be set up for a Business plan. Does that actually exist?

Because the Asana Sales just told me I could only create a new Free org and transfer all my data by way of the API.

I was considering two divisions — one premium, one business.

47

Hi @Daniel_Kreiss

In a free org, you can have several divisions, thus you could have 1 Premium Div + 1 Business Div in the free org.
I don’t see why you should create a NEW free org… because you can have only 1 org linked to a domain :thinking:
by “new” what do they mean?

48

@Daniel_Kreiss, I concur with all of @Julien_RENAUD’s reply, and agree you should find out more details about the Asana Sales suggestion…except I wasn’t clear about this:

because you can do this in Admin Settings:

image
image1062×294 26.9 KB

So maybe that’s part of the Asana Sales solution?

Larry

49

Thanks @lpb, let me clarify :wink:

1 org can have multiple domains associated to it.
But :wink: 1 domain can’t be associated to multiple orgs.

Is it clearer?

50

Yes, clearer, thanks.

I’m so tuned in to the model the notion never even occurred to me to try to associate a domain to more than one org!

Larry

51

So, if someone accidentally configures a division (or multiple) when trying to set up a new organization, how do we remove the divisions (one of which is paid; I cannot see how many exist) and get everyone into the same (paid) organization?

52

In these cases, the support can probably do it all for you.

1 Like
53

I was under the impression only Asana sales/support could set up a Division, not end users. @Julien_RENAUD is that incorrect - users can do it?

54

Yes only Asana can create Divisions, but users can create paid teams.

1 Like
55

Thanks for that clarification, @Julien_RENAUD.

And that doesn’t change anything for you, @Stephen_Nock - I agree with Bastien’s suggestion that you should contact Asana support to straighten things out.

1 Like
56

Yes, you’re right. If you find yourself “accidentally” in a Division instead of an Organization, it needs to be resolved by Asana Support. It should be straightforward to complete with a written request authorized by the Billing Admin. Thanks all for the support and the thorough documentation of the special Division option.

2 Likes
57

Hi everyone, we are right at the beginning of using/setting up Asana and maybe I could get some input on this still a little complicated division<=>team setup…

The total organisation has about 50 people who most certainly will not all use Asana.
We want to start using it in the marketing and products department that consists of 13-15 people. Since not all of them need to be able to have the full set of features and views we were thinking to split the licenses in 2 business and 11-13 premium.

Questions would be:

  • is this possible?
  • would the whole 13-15 people be able to collaborate on projects?
  • would this be a division with 2 teams then?
  • if new people want to start using Asana and do not belong to the deparment, they would be free?
  • could these be invited to collaborate on the divisions’ projects?
  • if new people join one of the teams, they would count to the charged seats?
  • would we have to get in touch with Asana support to create the division or would this be done automatically as soon as we have two paid teams with different licenses?

Thanks for your help! Again, a forum is much more helpful than the original documentation…
Best
Andreas

1 Like
58

Welcome, @anon97298569,

I’d say you have a good handle on Divisions!

The answers to all your questions are “yes” except the second and third: You’d have to do that as two Team plans; maybe they could be Divisions or Teams, not sure, but the point is they are separate plans and users in one would not be able to collaborate with the other.

Best to contact sales@asana.com with questions and support@asana.com to set up.

Larry

1 Like
59

Hi Larry,
thanks for your feedback!
To reflect that - we would have to have a business plan for one team and a premium plan for the other but would then not be able to collaborate on projects? This would then not make sense for us and we would have to put all in the business plan then?

Andreas

60

Hi @anon97298569

It will be possible to assign tasks to a person outside the team, but :

  • this person will not see the project name
  • this person will not see the other tasks
    so collaboration is complicated in this case.

Yes but only on tasks.
If you invite them to join a project, then it will take 1 additional license.

If teams need to collaborate with each other then having the same type of license is really the best solution.

Another piece of information: a division offers the possibility to create several teams within it. A paying team is the equivalent of a division with one team, so divisions offer more possibilities than a single team.

Julien

61

Thanks @Julien_RENAUD , one more clarification…

  • a DIVISION can have a number of TEAMS in it
  • these TEAMS can collaborate and see full projects and all tasks
  • these TEAMS can be on different licenses/plans or only on the same level?
  • if only on the same, we would not have to have TWO plans, but only ONE?
  • to make this happen, the ORGANIZATION has to be on a free plan?
  • a DIVISION cannot be created by the user but only on request by Asana?

I hope, I’ll get it someday…
Thanks!