Skip to Content
Browse documentation

Assign a UAPP MongoDB Database Role

Grant a supported MongoDB database role to a same-server user, understand additive grants and verify effective access before reducing privileges.

Open Databases → MongoDB → Assign User to MongoDB.

FieldRequirement
DatabaseExisting database in the account inventory.
Database UserExisting account user on the same server.
RoleOne offered role: read, readWrite, dbAdmin or dbOwner.

The form redirects to database/user creation when required inventory is missing. Cross-server assignment is rejected.

Choose and grant

read is the read-oriented choice; readWrite adds data-writing capability. dbAdmin provides database administration capabilities, while dbOwner is the broader ownership-level choice. These are role identifiers, not custom permission checkboxes. Confirm that the intended role fits the application's requirements and the provider's server configuration.

Select the pair and one role, review and submit. The helper grants that role on the selected database to the identity stored in the admin authentication database. Verify the recorded assignment and actual application operations.

Changing the selection does not replace earlier roles

The helper adds a role but the panel stores one role value for each user/database assignment. Choosing read after readWrite does not automatically revoke readWrite. Later removal revokes the currently recorded role, which can leave earlier roles in place. Ask the provider to reconcile effective roles before treating a change as an access reduction.

Assignment has no explicit demo guard. Removing an assignment is a separate action under MongoDB Databases. Database role assignment does not update the application password, listener, firewall or connection settings.