Remove a database user when its application, contractor or integration no longer requires access. This revokes that credential, but it does not delete the database itself. Check dependencies carefully because an active application can stop working immediately after its user is removed.
IN THIS ARTICLE
Prepare for the change
Identify every database and application using the account. A universal user may have broader access than its name suggests. If it is the only working application credential, create and test a replacement first.
01 Remove an unused database user in Plesk
- Open Databases > User Management for the correct subscription.
- Locate the exact username and review its database associations and default-user status. Compare the name with application configuration and scheduled jobs.
- If replacing it, update consumers to a tested new user with appropriate privileges. Verify application access before removing the old credential.
- If Plesk marks the user as the default for a database, assign an appropriate replacement or clear that default setting through the supported user form before removal. Keep at least one usable associated user where the database remains active.
- Select the unwanted user and choose Remove. Confirm the exact name, then remove its stored credential from retired automation and password records according to your retention process.
How do I confirm the removed database user is no longer used?
Test the application with the replacement account and confirm that new connections using the retired credential are rejected. Check recent application logs for authentication errors.
If the change does not work
If removal is blocked, inspect the default-user or managed-application relationship instead of deleting the database as a workaround. If a dependency was missed, restore access through a new or recreated authorized user and update its consumers. Recreating the username alone does not guarantee its previous privileges and host restrictions have returned.