Implementing Divisions

[lpb]

Welcome, @Hayley2,

Divisions can be complicated. For the full picture, see:

What I learned about divisions

Workspace, organization, division, we’ve all heard about it! But “division” is not the easiest one to understand [Update June 2023, thanks @lpb ] A new Guide article from Asana giving Divisions basic info in a clear way: And here is a summary of everything I have discovered over time on the subject! As an introduction, here is a quote from my friend @LEGGO, which is both a good summary and a good teaser for the rest of the post: “a division is like a collection …

They effectively create silos; you can collaborate among Division members within a Division, but not across Divisions with premium features.

You will pay for members in the two Divisions you mentioned. All others will be in the free Asana Basic plan.

@Hayley2

1. I assume that all of these projects would need to be moved to the new Client Services team to leverage these features.

Yes, you would have to move the projects. But you are not limited to one team. In each Division’s admin console, you can designate which teams are in the Division, so you may have more than one.

@Hayley2

2. I assume that my portfolios will remain intact provided the projects are under the Client Services Team.

Yes, I believe so.

@Hayley2

3. I assume that I will need to manually move these projects to the new location in order to retain their position and data in the relevant portfolio.

Same as 1.; or did you mean something different?

Again, this is complicated, and the above is the best of my knowledge, but I recommend you confirm with Asana Sales or Support before you change. And perhaps others will weigh in here; cc @Julien_RENAUD, Division Czar!

Thanks,

Larry