A database user is a MariaDB credential that can be granted access to one or more of your databases. Opterius lets you create additional users beyond the one created with each database — useful for giving a read-only reporting user access, or separating credentials between applications.
Creating an Additional User
Go to Hosting Mode → Databases → Database Users → New User.
Enter a username and password. The username will be prefixed with your account name (e.g., alice_reporter). The user is created in MariaDB with no privileges until you explicitly assign it to a database.
[!TIP] Use a separate database user per application. If one application's credentials are compromised, the others are not affected.
Assigning a User to a Database
From Hosting Mode → Databases → [database] → Manage Users, select a user from the dropdown and choose the privilege level:
| Privilege | What It Allows |
|---|---|
| ALL | Full read/write access, including DDL (CREATE TABLE, DROP TABLE, etc.) |
| SELECT only | Read-only access — useful for reporting tools or analytics queries |
| Custom | Manually select individual privileges |
Click Grant to apply. The grant takes effect immediately.
Changing a User's Password
Go to Hosting Mode → Databases → Database Users → [user] → Change Password.
Enter and confirm the new password. The change applies immediately — any open connections using the old password will not be dropped, but new connections must use the new password.
[!IMPORTANT] Update your application's database configuration after changing a password. Applications that cache the old credentials will fail to reconnect once their connection pool recycles.
Revoking Access to a Database
From Hosting Mode → Databases → [database] → Manage Users, click Revoke next to the user. This removes their privileges on that database without deleting the user. The user can still access other databases they have been granted access to.
Deleting a User
Go to Hosting Mode → Databases → Database Users → [user] → Delete.
Deleting a user revokes all their privileges and removes the MySQL user entirely. Any application still using those credentials will immediately lose database access.
[!WARNING] There is no undo. Make sure no running application depends on the user before deleting.