Skip to Content
Browse documentation

Assign a UAPP MySQL User to a Database

Grant all or selected database privileges to an account-owned MySQL user on the same server and understand additive grant behavior.

Open Databases → MySQL → Assign User to Database.

Both an existing account database and a database user are needed. If either inventory is empty, the page redirects to the relevant creation workflow.

FieldRequirement
DatabaseRequired existing account database.
UserRequired existing account user on the same server as the database.
PrivilegesAll privileges or at least one selected custom privilege. All is initially selected.

Supported custom privileges are ALTER, ALTER ROUTINE, CREATE, CREATE ROUTINE, CREATE TEMPORARY TABLES, CREATE VIEW, DELETE, DROP, EVENT, EXECUTE, INDEX, INSERT, LOCK TABLES, REFERENCES, SELECT, SHOW VIEW, TRIGGER and UPDATE.

Grant and verify

Select the database/user pair, choose only the intended privileges, review and submit. The server checks account inventory and rejects assignment across different servers. Verify the result in MySQL Databases and test the application's required operations.

Granting fewer privileges is not a revoke

This helper issues a GRANT operation. Reassigning with fewer selections does not necessarily remove earlier server privileges, even if recorded assignment details show the new selection. Use the explicit removal workflow and carefully grant the intended set when reducing access, coordinating application interruption.

Assignment removal is a separate action under MySQL Databases. It removes database access rather than deleting the login. Confirm effective privileges with the provider if recorded details and actual behavior differ.

The assignment view has no explicit demo guard. A successful grant does not configure the application's password, source host, network access or database schema.