Groups are now projects in the organizations and projects hierarchy.
You can create multiple projects in an organization.
By having multiple projects within an organization, you can:
Isolate different environments (for instance, development/qa/prod environments) from each other.
Associate different users or teams with different environments, or give different permissions to users in different environments.
Maintain separate cluster security configurations. For example:
Create/manage different sets of database user credentials for each project.
Isolate networks in different VPCs.
Create different alert settings. For example, configure alerts for Production environments differently than Development environments.
When you create a project, you are added as an
Project Owner for the project.
To view a project, you must either:
When you move a project to another Atlas organization, Atlas copies the project users and their respective roles to the same project in the destination organization. However, Atlas doesn't carryover teams assigned to the project because you define teams at the organization level.
To move a project to another Atlas organization, you must be an
Organization Owner for both the current and the destination
To move a project for an organization:
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
Click the Leaf icon in the upper left corner of the page. You can also expand the Projects menu in the navigation bar, then click View All Projects.
Billing a Moved Project
Organization Owner of two different Organizations
can move projects between those Organizations at any time. Usage in
any particular project during any particular hour is accrued to the
Organization under which the project was at that time.
Organization Owner owns the Telecomm and
Storage Organizations in Atlas. They decide to move
their Backup project from Telecomm to Storage at
The Telecomm project is billed for the full 11:00 to 11:59 am hour. Storage starts getting billed at 12:00 pm.
Atlas removes existing API Keys after moving the Project. You must create a new API Key after moving the Project.
The project has no outstanding invoices.
The project has no configured private endpoint connections.
The project has no active federated database instances.