Identify the exact database, the operations the application needs and the host from which it connects. Avoid a universal user spanning all databases when one database is sufficient. Check that the application supports the intended password and connection method.

1. Open Databases > User Management and select the add-user action.
2. Enter a distinct username and strong unique password. Select the intended database rather than the option for access to all databases.
3. Review the available role or permission set. A reporting connection may need read-only access, while an application installer may temporarily require schema changes. Choose privileges that fit the actual task.
4. Configure remote-access restrictions when available. Permit only the required client host or network and coordinate database-server and firewall access with the administrator.
5. Save the user and enter its credentials in the authorized application configuration or client. Keep secrets out of support messages and public repositories.

Test the required operation using this user, including a permitted write if the application needs one. Confirm that it cannot access an unrelated database. Keep the existing working user until a planned credential migration has been tested.

For access-denied errors, check the full username, selected database, source host and permissions. A successful network connection does not prove that authentication or authorization is correct. If you are replacing a compromised credential, update all consumers and retire the old user after verifying the replacement.

• Creating a website database in Plesk
• Removing an unused database user in Plesk
• Exporting and downloading a database dump in Plesk
• Removing an unused database in Plesk

• Plesk: Managing Database User Accounts