Plan change and problems with support

[anon91170507]

Partial response here:

1. First of all, are you sure we are talking about literal “Teams”? If so, this appears incorrect: “Support explained to me that, by proceeding team by team, if a person is present in more than one team, we would have to pay for their seat more than once.” That might make sense for Workspaces or Organizations. NOT for Teams. Anybody can be part of 100 Teams with only 1 seat payable.

2. For such a small non-profit org as you have, there may be little or no reason to even have Teams at all. [Other than a single one, I mean…that is unavoidable.] Only have different Teams if you want the functionality that you derive from it, which IMO is quite limited. I’d recommend starting with a single Team for the whole org and then only consider further Teams if you really find you need them.

3. You probably don’t want or need multiple Workspaces or Organizations. Don’t create multiples here until/unless you find that a single one doesn’t work for you. It will be way easier to create your 2nd such entity later than to have multiples now and try to merge later.

So, I’d recommend carefully clarifying whether you are talking about Teams, Workspaces, Organizations, or something else. Start with the simplest structure possible, and simply add poeple there.

Try these resources:

How to Bar the Door (or, How to keep everyone with your company email domain from joining your Asana Organization)

Most people set up their Asana implementation as an Organization (as opposed to a Workspace), and for good reason - there are many benefits to an Organization over a Workspace. One property of an Organization is that anyone who has an email address based on the email domain of the Organization can join that Organization without asking for or obtaining any sort of approval. In some cases this can be viewed as a good thing in terms of convenience and ease of onboarding. However, it’s important t…

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 …

Divisions

Organization vs Workspace Profiles

Hi @Lia_Sparks , sorry for the delay getting back to you! So regarding the yellow dots on each org/workspace from your profile drop down; those simply show you that you have notifications in your relevant Inboxes. Since you have all these listed under your profile, that means they are already connected under your Asana account; you have one Asana account which you can log in to using any of the email addresses that you have associated to each of these orgs/workspaces. You can see a list of al…

Members vs. limited members vs. guests

Hi all - I have created a workspace using a Gmail account. I paid for 2 seats, but need to invite guests outside of the work Gmail account. However, anytime I add someone, it counts them as a member or limited member (and not as a guest). Asana is now saying we are over our seat limit. Is this because the “guests” I tried to invite also use Gmail? How can I avoid this? I only have 2 people in my small business and need a few others to access short-term projects. Thank you for your help.

Good luck!