Español
Deutsch
Every database has its own separate set of users and permissions — distinct from your Plesk login, and worth understanding for both security and troubleshooting.
Why Databases Have Their Own Users
Separating database access from your hosting login lets you grant a specific application (like a WordPress install) only the access it actually needs, without exposing your full hosting account credentials.
Common Permission Types
SELECT (read data), INSERT (add new data), UPDATE (modify existing data), and DELETE (remove data) are the core permissions most applications need. Additional permissions exist for more advanced structural changes.
The Principle of Least Privilege
A database user should only have the permissions it actually needs to function. A read-only reporting tool, for example, doesn't need DELETE permission — limiting scope reduces the damage possible if that specific access is ever compromised.
Managing Users in Plesk
Plesk's database section lets you view and manage the users associated with each database, including resetting passwords and adjusting permissions without needing to write SQL commands directly.
When to Create a New Database User
Each separate application connecting to a database should ideally have its own user, rather than sharing credentials — this makes it far easier to track down which application is responsible if something goes wrong.
