In the free org, there is a limit of users per team, but you can create several teams.
According to me, there is no limit on the total number of free users.
So you can have for instance 50 free users, but in several teams.
Asana sales should be contacted to check that.
Thanks, @Julien_RENAUD. All of the published info on the Personal plan just says a limit of 10 users, like the 500 user limit for Starter and Advanced, but perhaps it’s still by teams as it was for the Basic plan (15 max per team, but you could have multiple teams).
I’m checking with Asana 
I’ll keep you posted
Asana has confirmed my previous answer 
The “10 limit” is per team
@Julien_RENAUD @lpb That sounds reasonable for large enterprises! Now I can rest easy 
. Thanks for the awesome support!
Thanks, @Julien_RENAUD,
I just submitted a Help Center Request because:
Maybe you can mention to your contact that Asana Pricing | Personal, Starter, Advanced, & Enterprise plans • Asana is misleading and the info you learned is not available without a contact, apparently.
Thanks,
Larry
Hi everyone,
We have a customer experiencing an issue with their division account. They noticed that people with the same domain—but who are not part of their team—are being automatically added to their division account or team.
From what I understand, joining a division should only be possible by invitation, which Asana has also confirmed. However, I found that anyone in the team or division can invite others. Could this be causing the issue?
Additionally, when they created a custom field and added it to their library (which is named after their domain rather than their division), they expected it to be accessible only within their division—essentially working like a global field but restricted to division members. However, they found that people outside their division could see and use the field.
We tried adjusting the field’s member settings to remove organization-wide access, but there was no option to do so. As a workaround, we changed the organization’s permission to “user.”
Another challenge they faced is that they cannot create a custom field with the same name as an existing one, even within their division. For example, if a “Priority” field already exists globally, they must create a uniquely named version (e.g., “*Priority”) instead of simply using “Priority” within their division.
Is there a way to ensure that custom fields are available globally within a division but not accessible to members outside the division?
Thank you.
Hi @KNicks_8571d0, I’m sorry to hear about these issues. While we don’t have access to account details here in the Forum, I’m happy to share some general insights on divisions.
A division is a selection of teams within a free organization under a single subscription, but it’s not a fully separate environment. Anyone in the same domain can be added to a team within a division if settings allow it, and organization members added to projects within a paid division will also take up a seat, even if they are not a full member of that division.
If your customer has an Enterprise or Enterprise+ division, they can use access management features to control membership, but this isn’t available in lower tiers.
For custom fields, only local (project-level) and global (organization-wide) options exist at the moment. It’s not possible to restrict custom fields to just a division while keeping them global within that division, but there’s already a Product Feedback thread where you can add your vote. Also, custom field names must be unique across an organization to avoid confusion.
To help them sort these issues out, I’d recommend having them reach out to our Support team. Support has access to account details and will be better equipped to advise them based on the details of their plan and setup.
I hope this helps! 
Hi Vanessa,
Thank you for the information.
I found a workaround for the custom fields issue. Since they’re on the Enterprise plan, I suggested creating a bundle so they could use the same custom field name. However, they want to use the custom fields in My Tasks, so we’ll need to go back to using the global custom field. The good news is, we can make the global custom field private, so only members added to it will be able to see and use it. They’ll just need to use a different, unique name for the custom field, but this should work fine.