Manage Project Access

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.

Create a Project

Prerequisites

To create a project for an organization, you must be either an Organization Owner or an Organization Project Creator.

When you create a project, you are added as an Project Owner for the project.

Procedure

In Atlas, go to the All Projects 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 All Projects under the Identity & Access Header.

The All Projects page for your organization displays.

Go to the Create a Project page.

Do one of the following steps:

Click New Project.
Expand the Projects menu in the navigation bar, then click + New Project.

Name your new project.

Enter the name for your new project.
Important
The project name has the following limits:
- Can't exceed 64 characters.
- Restricted to letters, numbers, spaces, dashes, and underscores.
Don't include sensitive information in your project name.
Click Next.

Add members.

For existing Atlas users, enter their username. Usually, this is the email the person used to register.
For new Atlas users, enter their email address to send an invitation.

Specify the access for the members.

Click Create Project.

View Projects

Prerequisites

To view a project, you must either:

Be an Organization Owner or Project Owner
Receive an invitation that grants access to the project. An Organization Owner or Project Owner can invite users to projects.

Important

Project Invitation Deprecation

The Atlas release on September 13, 2023 deprecates project invitations.

When you invite an organization member to projects within the organization, the user is automatically granted access to those projects and doesn't receive any invitations. When you invite a user to projects in an organization that the user doesn't belong to, the user receives a single invitation to the organization, which includes access to all of the projects that you grant them access to. Invitations expire after 30 days.

Procedure

In Atlas, go to the All Projects 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 All Projects under the Identity & Access Header.

The All Projects page for your organization displays.

A Backup Compliance Policy icon appears next to each project name that has a Backup Compliance Policy enabled.

Update a Project

You can update project details such as the project name and tags.

Prerequisites

To update a project, you must have Project Owner access to the project.

Procedure

In Atlas, go to the Project Settings page.

If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
In the sidebar, click the icon next to Project Overview.

The Project Settings page displays.

Update project details.

You can update the project name and tags in the Project Settings page.

Click Save Changes.

Move a Project

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 carry over teams assigned to the project because you define teams at the organization level.

When you move projects across organizations, your changes take effect immediately. The move doesn't:

Impact cluster uptime or current cluster configuration.
Cause downtime for your cluster or changes to your connection string.

Atlas carries over VPC peering connections and private endpoint configurations to the destination organization. You don't need to recreate them.

Important

Atlas removes existing API Keys after moving the project. You must create a new API Key after moving the project.

Prerequisites

To move a project to another Atlas organization, you must be an Organization Owner for both the current and the destination organization.

Procedure

To move a project for an organization:

In Atlas, go to the All Projects 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 All Projects under the Identity & Access Header.

The All Projects page for your organization displays.

Select the project you want to move.

For the project you want to move:

Click .
Click Move Project.

The Move Project dialog box appears.

Select the target organization. Click Next: Confirm to go to the confirmation screen.

Click Confirm & Move.

Note

Billing a Moved Project

An 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.

For example, an Organization Owner owns the Telecomm and Storage Organizations in Atlas. They decide to move their Backup project from Telecomm to Storage at 11:40 am.

The Telecomm project is billed for the full 11:00 to 11:59 am hour. Storage starts getting billed at 12:00 pm.

Delete a Project

When you delete a project, Atlas guides you through a deletion wizard that lists the project's resources and deletes them for you. You don't need to terminate clusters, applications, or other resources before you start.

Warning

Deleting a project is irreversible. Atlas permanently deletes all project data, including clusters, configurations, backup snapshots, search indexes, application data, and stream processors. You can't recover deleted data.

Prerequisites

To delete a project for an organization, you must either have the Project Owner role for the project or have the Organization Owner role for the project's organization.
The project has no outstanding invoices.
The project doesn't have an enabled Backup Compliance Policy. To delete the project, the authorized point of contact must first contact MongoDB Support and request that they disable the Backup Compliance Policy.
The project wasn't created through a third-party partner, such as Vercel. To delete a project that a third party created, delete the project in that third party's interface.

Procedure

You can delete from the organization's Projects view or the project's Project Setting view.

To delete a project from the organization's Projects view:

In Atlas, go to the All Projects 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 All Projects under the Identity & Access Header.

The All Projects page for your organization displays.

For the project you want to delete, click .

If the project contains no resources, Atlas opens a confirmation modal. Enter the project name, then click Delete Project. Otherwise, Atlas opens the project deletion wizard.

Complete the recommended actions.

The Recommended Actions step lists the data governance tasks that MongoDB recommends you complete before you delete the project:

Export your most recent backup snapshot.
Export your audit logs.
Export your Project Activity Feed events.
Disconnect third-party integrations to remove their API keys.

Select the acknowledgement checkbox, then click Proceed to required actions.

Review the project data that Atlas deletes.

The Review project data step lists the resources in the project that Atlas permanently deletes:

Clusters, including Flex clusters and Free clusters
Atlas App Services applications
Federated database instances
Atlas Stream Processing workspaces
Private endpoints
AI model API keys

Expand each card to review its individual resources.

Acknowledge the required actions.

In the Required actions section, select all three checkboxes to confirm that Atlas:

Permanently deletes all project data, which you can't recover.
Overrides Termination Protection for all clusters and deletes online archives, backup snapshots, stream processors, and connections.
Revokes access to federated database instances, which might disrupt your applications.

Click Delete project forever.

Atlas deletes the project and returns you to the All Projects page.

To delete from the project's Project Setting view:

In Atlas, go to the Project Settings page.

If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
In the sidebar, click the icon next to Project Overview.

The Project Settings page displays.

In the Delete Project section, click Delete Project.

If the project contains no resources, Atlas opens a confirmation modal. Enter the project name, then click Delete Project. Otherwise, Atlas opens the project deletion wizard.

Complete the recommended actions.

The Recommended Actions step lists the data governance tasks that MongoDB recommends you complete before you delete the project:

Export your most recent backup snapshot.
Export your audit logs.
Export your Project Activity Feed events.
Disconnect third-party integrations to remove their API keys.

Select the acknowledgement checkbox, then click Proceed to required actions.

Review the project data that Atlas deletes.

The Review project data step lists the resources in the project that Atlas permanently deletes:

Clusters, including Flex clusters and Free clusters
Atlas App Services applications
Federated database instances
Atlas Stream Processing workspaces
Private endpoints
AI model API keys

Expand each card to review its individual resources.

Acknowledge the required actions.

In the Required actions section, select all three checkboxes to confirm that Atlas:

Permanently deletes all project data, which you can't recover.
Overrides Termination Protection for all clusters and deletes online archives, backup snapshots, stream processors, and connections.
Revokes access to federated database instances, which might disrupt your applications.

Click Delete project forever.

Atlas deletes the project and returns you to the All Projects page.

Manage Projects with the Atlas CLI

You can use the Atlas CLI to manage projects programmatically.

Create a Project

To create a new project using the Atlas CLI, run the following command:

atlas projects create <projectName> [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas projects create.

View Projects

To list all projects using the Atlas CLI, run the following command:

atlas projects list [options]

To return the details for the project you specify using the Atlas CLI, run the following command:

atlas projects describe <ID> [options]

To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for atlas projects list and atlas projects describe.