UAPP MongoDB
Manage account-owned MongoDB databases, users and database roles with server placement, authentication scope and removal requirements in UAPP.
Open Databases → MongoDB. The sidebar requires the MongoDB feature and detected service availability; the views also check the feature.
| Menu | Purpose |
|---|---|
| MongoDB Databases | Review server placement, assigned users and database removal. |
| MongoDB Users | Review logins, rotate passwords and delete unassigned users. |
| Create MongoDB Database | Create a prefixed database on a configured server. |
| Create MongoDB User | Create a prefixed user in the admin authentication database. |
| Assign User to MongoDB | Grant a selected database role to a user on the same server. |
Create database and user on the same server, assign the intended role, then configure your application with full names and the correct authentication source. A user created here initially has no assigned database roles.
Scope and precautions
Inventory lookups are scoped to the signed-in hosting account. Server choices depend on active configuration and available authentication files. The creation views do not explicitly enforce a database-count ceiling; review provider allowances.
Database creation and role assignment have no explicit demo guard. User creation/password changes can still submit with generated passwords in demo mode. Database deletion, user deletion and assignment removal explicitly block demo requests.
Preserve data and review effective roles
Database deletion removes collections and data. Password and role changes can interrupt applications. Preserve required recovery data and verify effective server roles rather than relying only on the panel's recorded assignment label.
The panel records management outcomes, not application connectivity or data integrity. Server operations and inventory updates are separate steps; check for partial results after failure before retrying.