In the organizations and projects hierarchy, an organization can contain multiple projects (previously referred to as groups). Under this structure:
Billing happens at the organization level while preserving visibility into usage in each project.
You can view all projects within an organization.
You can use teams to bulk assign organization users to projects within the organization.
If you need to scale beyond the existing project limits, you can create multiple organizations.
Required Access
To perform any of the following actions, you must have
Organization Owner access to Atlas.
Create Multiple Organizations
Repeat the following steps to create multiple organizations:
Enter the name for your organization.
Important
Don't include sensitive information in your organization name.
Select Atlas and click Next.
You have the option of adding a new Cloud Manager organization or a new Atlas organization. For more information on Cloud Manager see the documentation.
(Optional) Disable the IP access list requirement for the Atlas Administration API.
When you create a new organization with the Atlas UI, Atlas requires IP access lists for the Atlas Administration API by default. If you require an IP access list, your Atlas Administration API keys can make API requests only from the location-based IP or CIDR addresses that you specify in the IP access list.
To disable the IP access list requirement and allow your Atlas Administration API keys to make requests from any address on the internet, toggle Require IP Access List for the Atlas Administration API to OFF.
To learn more, see Optional: Require an IP Access List for the Atlas Administration API.
(Optional) Set Up Cross-Organization Billing
You can set up cross-organization billing to share a billing subscription across multiple organizations.
The following prerequisites and limitations apply:
A paying organization must have an Atlas subscription.
To link an organization to a paying organization, you must have
Organization Billing AdminorOrganization Ownerprivileges for both organizations.For an organization to be linked to a paying organization, it must have the same minimums, uplifts, and SLA for their subscription plan as the paying organization or have no support plan (Atlas Basic).
A paying organization and any linked organizations or any organizations intended to be linked:
Can't have failed payments.
Can't have an active self-serve support plan.
Can't have an active self-serve marketplace subscription.
Can't have overlapping monthly commitment subscriptions.
To configure a paying organization and link other organizations to it:
(Optional) In Atlas, create an organization to configure as a paying organization.
If you wish to create a new organization through which to pay, Create an Organization.
Note
You can rename an organization to reach your desired cross-organization configuration.
In Atlas, go to the Linked Organizations page for your organization.
If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.
In the sidebar, click Linked Organizations under the Billing header.
The Linked Organizations page displays.
Select organizations to link to your paying organization.
A dialog box displays your selected organization under Paying organization on the left and a list of organizations you may link to it under Select organizations to link on the right.
Select each organization you wish to link to your paying organization.
Click Review and Finish.
Grant Project Access to your Organizations
To manage projects in all your organizations, you need to grant each organization programmatic access to the projects. You can use service accounts or API keys. To learn about service accounts versus API keys, see Get Started with the Atlas Administration API.
Repeat the steps to create a service account
for each project. The service account you create for a project gets
automatically added to the parent organization with the permission Organization Member.
Create an API key for each organization.
Repeat the steps to create an API key for an organization for each organization.
Invite the organization key to each project within the organization.
For each project within an organization, invite the related organization key.