Configure Database Users¶

Create database users to provide clients access to the clusters in your project. A database user's access is determined by the roles assigned to the user. When you create a database user, the user is added to all clusters in your Atlas project.

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 database user 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.

Note

If you require more than 100 database users on a project, please contact Atlas support.

Important

Atlas rolls back any user modifications not made through the UI or API. You must use the Atlas UI or API to add, modify, or delete database users on Atlas clusters.

Database User Authentication¶

Atlas offers the following forms of authentication for database users:

SCRAM is MongoDB's default authentication method. SCRAM requires a password for each user.

The authentication database for SCRAM-authenticated users is the admin database.

Add Database Users¶

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.

Select an authentication mechanism and follow the steps to create a new database user.

1

Open the Add New Database User dialog.¶

In the Security section of the left navigation, click Database Access. The Database Users tab displays.
Click Add New Database User.

2

Select Password.¶

In the Authentication Method section of the Add New Database User modal window, select the box labeled Password.

3

Enter user information.¶

Under Password Authentication, there are two text fields.

Enter a username for the new user in the top text field.
Enter a password for the new user in the lower text field.

To use a password auto-generated by Atlas, click the Autogenerate Secure Password button.

4

Assign user privileges.¶

You can assign privileges to the new user in one of the following ways:

Select Atlas admin from the Database User Privileges dropdown menu, which provides the user with readWriteAnyDatabase as well as other administrative privileges.
Select Read and write to any database, which allows the user to read from and write to any database.
Select Only read any database, which allows the user to read from any database.
If you have any custom roles defined, you can select Select pre-defined custom roles, then choose a role from the Pre-defined Custom Role dropdown menu. To learn more about custom roles, see Configure Custom Roles.
Select Grant specific privileges to assign the user privileges on individual databases and collections.
Note
When applied to a collection, the read and readWrite roles in Atlas differ slightly from the built-in MongoDB read and readWrite roles.
In Atlas, read provides the following collection-level actions:
In Atlas, readWrite provides the same actions as read, as well as the following additional collection-level actions:
For more information on authorization, see Role-Based Access Control and Built-in Roles in the MongoDB manual.

5

Optional: Specify the resources in the project that the user can access.¶

By default, users can access all the clusters and Atlas Data Lakes in the project. You can restrict access to specific clusters and Atlas Data Lakes by doing the following:

Toggle Restrict Access to Specific Clusters/Data Lakes to ON.
Select the clusters and Atlas Data Lakes to grant the user access to from the Grant Access To list.

6

Optional: Save as temporary user.¶

Toggle Temporary User to On and choose a time after which Atlas can delete the user from the Temporary User Duration dropdown. You can select one of the following time periods for the user to exist:

6 hours
1 day
1 week

In the Database Users tab, temporary users display the time remaining until Atlas will delete the user. Once Atlas deletes the user, any client or application that uses the temporary user's credententials loses access to the cluster.

7

Click Add User.¶

You can also add database users through the Atlas API. See Create a Database User.

Modify Database Users¶

To modify existing users for an Atlas project:

In the Security section in the left navigation, click Database Access. The Database Users tab displays.
Click Edit for the user you want to modify. You can modify the privileges and authentication details assigned to the user. You cannot modify the authentication method.
- For SCRAM authenticated users, you can edit a user's password.
- For X.509 certificate authenticated users, you can download a new certificate.
- For AWS IAM users, you can only modify database access privileges.
For temporary users, you can also modify the time period the user exists or make the user a permanent user, provided the user's expiration date has not already passed.
Note
You cannot change a permanent user into a temporary user. If you change a temporary user into a permanent user, you cannot make it temporary again.
Click Update User to save the changes.

You can also modify existing users through the Atlas API. See Update a Database User.

Delete Database Users¶

To delete existing users for an Atlas project:

In the Security section in the left navigation, click Database Access. The Database Users tab displays.
Click Delete next to the user you want to delete.
Click Delete again to confirm.

You can also delete existing users through the Atlas API. See Delete a Database User.

Database User Privileges¶

The following table describes the Database User Privileges and the MongoDB Built-in Roles or privilege actions they represent.

Note

Protected MongoDB Database Namespaces

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

admin
local
config

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

Database User Privilege	MongoDB Role	Inherited Roles or Privilege Actions
`Atlas admin`¶	`atlasAdmin`¶	`readWriteAnyDatabase` `readAnyDatabase` `dbAdminAnyDatabase` `clusterMonitor` `cleanupOrphaned` `enableSharding` `flushRouterConfig` `moveChunk` `splitChunk` `viewUser`
`Read and write to any database`¶	`readWriteAnyDatabase`¶	`readWriteAnyDatabase`
`Only read any database`¶	`readAnyDatabase`¶	`readAnyDatabase`

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

Give Feedback

← Configure IP Access List Entries Configure Custom Roles →