Docs Menu

Docs HomeMongoDB Atlas

Configure Database Users

On this page

  • Database User Authentication
  • Required Access
  • Add Database Users
  • View Database Users and Certificates
  • Modify Database Users
  • Delete Database Users
  • Built-in Roles
  • Specific Privileges

Create database users to provide clients access to the database deployments in your project. A database user's access is determined by the roles assigned to the user. When you create a database user, any of the built-in roles add the user to all database deployments in your Atlas project. You can remove the default built-in role and set specific privileges and custom roles to add the user to specific database deployments.

Database users are separate from Atlas users. Database users have access to MongoDB databases, while Atlas users have access to the Atlas application itself. Atlas supports creating temporary database users that automatically expire within a user-configurable 7-day period.

Atlas audits the creation, deletion, and updates of database users in the project's Activity Feed. Atlas audits actions pertaining to both temporary and non-temporary database users. To view the project's Activity Feed, click Activity Feed in the Project section of the left navigation. For more information on the project Activity Feed, see View All Activity.

The available Atlas built-in roles and specific privileges support a subset of MongoDB commands. See Unsupported Commands in M10+ Clusters for more information.

Atlas supports a maximum of 100 database users per Atlas project. If you require more than 100 database users on a project, contact Atlas support.


You must use the Atlas CLI, Atlas Administration API, Atlas UI, or a supported integration to add, modify, or delete database users on Atlas database deployments. Otherwise, Atlas rolls back any user modifications.

Atlas offers the following forms of authentication for database users:

To add database users, you must have Organization Owner or Project Owner access to Atlas.

A project can have users with different authentication methods.

You cannot change a user's authentication method after creating that user. To use an alternative authentication method, you must create a new user.

The following table describes the Atlas built-in roles and the MongoDB Roles or privilege actions they represent.


Protected MongoDB Database Namespaces

The following databases are read-only for all users, including those with the atlasAdmin or clusterMonitor role.

  • local

  • config

We discourage writing to the admin database. Atlas manages multiple collections in the admin database, and these collections are read-only for all users.

atlasAdmin has the update privilege on the config.settings collection to manage the balancer.

Atlas Built-in Role
MongoDB Role
Inherited Roles or Privilege Actions
Atlas admin
Read and write to any database
Only read any database

To learn more about common commands that Atlas doesn't support with the current Atlas user privileges, see Unsupported Commands in M10+ Clusters

The following table describes the Atlas specific privileges, the database it applies to, and the privilege actions they represent.

Atlas Specific Privilege
Privilege Actions
User configured
User configured except local and config
User configured
User configured
User configured
User configured except local and config
User configured except local and config
←  Configure Database Deployment Authentication and AuthorizationConfigure Custom Database Roles →
Share Feedback
© 2023 MongoDB, Inc.


  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2023 MongoDB, Inc.