Revoking access removes all of a user's privileges on a specific database. The user still exists but can no longer query, read, or modify that database in any way. The Nobregas MySQL Panel makes revocation a two-click process with a confirmation step.
When to Revoke Access
- A project has ended and the user no longer needs the database.
- An employee or contractor has left the team.
- You are consolidating databases and decommissioning old ones.
- A security incident requires immediately cutting off access.
- You granted access by mistake and need to undo it.
Step-by-Step: Revoking Access
- Log in at mysql.nobregas.org.
- Go to Database Users in the top navigation bar.
- Click the Manage button on the user whose access you want to revoke.
- In the Current Grants section, find the database to revoke.
- Click the Revoke button next to that grant.
- A confirmation dialog appears asking you to confirm the revocation.
- Click Confirm to proceed.
The grant is immediately removed from MySQL.
What Happens After Revocation
- The user loses all privileges on that specific database.
- Any active connections using that grant will fail on the next query attempt.
- The user still exists and retains access to any other databases they are granted.
- The revocation takes effect immediately — no server restart required.
Revoke vs. Delete
| Action | What It Does |
|---|---|
| Revoke | Removes access to one specific database. User still exists. |
| Delete User | Removes the entire user account and all its grants. |
Use Revoke when you want to remove access to a single database while keeping the user active for other databases.
Can You Undo a Revoke?
Revocation cannot be undone with a single click. To restore access, you must add a new grant using the Add Database Access section in the Manage modal. You will need to re-select the database and configure the privileges again.
Revoking All Access
If you want to remove a user's access to every database:
- Open the Manage modal.
- Revoke each database grant one by one.
- The user will remain in the system with no database access.
Alternatively, if you no longer need the user at all, simply Delete the user from the Database Users page.
Security Best Practice
Revoke access immediately when it is no longer needed. Stale grants — permissions that outlive their purpose — are one of the most common causes of unauthorized data access. Regular privilege audits help keep your databases secure.
