View/Modify Project Settings

Required Access

To view project settings, you must have Project Owner access to the project. To modify project settings, click Settings, then Project Settings.

View/Modify Project Settings

Project settings apply to all the users in the project [1]. The Project ID displayed at the top of the page is used by the Atlas API.

You can set the following:

Setting Description

Sets your project’s name.


Only a user with Owner role for the project or the Organization Owner role for the project’s organization can edit the project name.

Project Time Zone Sets your project’s time zone. This does not affect the timezones set for individual user accounts. [1]
Using Custom DNS on AWS with VPC peering

Allows you to expose a second connection string for your dedicated Atlas clusters on AWS that resolves to private IPs.

Enable this setting if you use custom DNS that cannot take advantage of AWS built-in split-horizon DNS across a VPC peering connection.


Atlas displays this setting only when you enable network peering on AWS.

Connect via Peering Only (GCP and Azure)

Allows you to enable or disable connections between MongoDB Atlas dedicated clusters and public IP addresses outside of the peered VPC/VNet. You can only enable or disable this setting when there are no active dedicated GCP or Azure clusters in your Project.

Feature Deprecated

This feature has been deprecated. Use Split Horizon connection strings to connect to your cluster. These connection strings allow you to connect using both VPC/VNet Peering and whitelisted public IP addresses. To learn more about support for Split Horizon, see this FAQ.

Collect Database Specific Statistics Allows you to enable or disable the collection of database statistics in cluster metrics.
Set Preferred Cluster Maintenance Start Time

Set which hour of the day that Atlas should start weekly maintenance on your cluster.

If you toggle to On, click pencil icon to set the Maintenance Start Time. Atlas displays this time in the time zone you set in your Profile.

Maintenance Window Considerations

Urgent Maintenance Activities Cannot Wait

Urgent maintenance activities such as security patches cannot wait for your chosen window. Atlas will start those maintenance activities when needed.

Once maintenance is scheduled for your cluster, you cannot change your maintenance window until the current maintenance efforts have completed.

Maintenance Requires Replica Set Elections
Atlas performs maintenance the same way as the manual maintenance procedure. This requires at least one replica set election during the maintenance window per replica set.
Maintenance Starts As Close to the Hour As Possible
Maintenance always begins as close to the scheduled hour as possible, but in-progress cluster updates or expected system issues could delay the start time.

When maintenance is required, Atlas:

  • Displays a banner in your cluster list showing the date and time when the maintenance is scheduled.

  • Sends a notification email to all users in the project 72 hours before the scheduled maintenance.


    To configure how you receive scheduled maintenance window notifications, see Configure a Maintenance Window Alert.

With this information, you can choose one of three options:

  1. Do nothing. The maintenance occurs during your scheduled maintenance window.
  2. Begin Maintenance Now. The scheduled maintenance starts immediately. If you choose this option, you are asked to confirm it in a separate modal.
  3. Defer Maintenance for One Week. The scheduled maintenance starts during your preferred maintenance window one week after the given scheduled maintenance date and time. If you choose this option, you are asked to confirm it in a separate modal.
Real Time Performance Panel Allows you to see real time metrics from your MongoDB database.
Data Explorer Allows you to query your database with an easy to use interface.
Performance Advisor Allows you to analyze database logs to recommend performance improvements.
Delete Charts


Deleting a MongoDB Charts instance deletes all data associated with that instance including dashboards, data sources, and metadata. Once the MongoDB Charts instance is deleted, this data cannot be recovered.

Allows Project Owners to delete the MongoDB Charts instance associated with your project. This setting is only visible if you have created a Charts instance for your project.

If you delete your linked MongoDB Charts instance, you can create a new MongoDB Charts instance for your project at any time. The newly created instance does not retain any data from previously deleted instances.

Delete Project The DELETE button allows you to delete a project.
[1](1, 2) To modify your user settings, click on your user name in the upper-right hand corner and select Account.