Multi-org deployment

Asana enables the seamless collaboration of teams across entire organizations. For customers with stringent data segregation requirements multi-org deployment offers these organizations the ability to keep their data distinct and isolated. This means that customers have the option to have one email domain tied to multiple Asana orgs, enabling them to categorize and split teams and data into sub-orgs.

Available to organizations on Asana Enterprise+ tiers.

Visit our pricing page for more information.

Who is it for?

Multi-org deployment is for organizations with the need to satisfy their data residency, Health Insurance Portability and Accountability Act (HIPAA), and enterprise key management (EKM), to comply with regional data protection and privacy laws.

This allows customers to expand their Asana presence to multiple geographical regions within a single existing Asana deployment and comply with local data requirements. Multi-org deployment also enables data isolation and admin separation as well as admin control at each sub-level organization. 

This feature resolves issues for:

  • Organizations needing a hard separation of data, for example when regulations require total separation of data between business units (ie; investment banks.)
  • Organizations needing data from different geographical units to be stored in different data centers
  • When organizations can only enforce controls like EKM or HIPAA on certain parts of their org

Setting up sub-organizations

Once migrated to multi-org deployment be sure to review all the settings in the admin console for your Asana sub-orgs.

From the settings tab, choose unique org names and specific logos to clearly distinguish between each sub org. 

  • Example: If you have multiple business units with distinct data residency needs, label the orgs accordingly to highlight their regions, so members in more than one org know which org they are working in. (Org1: Acme Org - US, and Org2: Acme Org - EU)

When using multi-org deployment it is important to note:

  • When a new sub-org is created, it will be blank and users will need to be invited in order to access it
  • There will still be a primary organization that all users have access to (and where new autojoin users will land)
  • Any changes on SAML & Google SSO will affect all Asana orgs linked to your email domain

Please contact our sales team to opt-in for multi-org deployment.



Was this article helpful?

Thanks for your feedback