Database privileges determine what an application user can do within an assigned database. The right permission set depends on whether the account serves ordinary requests, runs schema upgrades or performs read-only reporting.
IN THIS ARTICLE
Check access and requirements
Read the application requirements and record the existing grants. Confirm the full database and username. Keep a backup before a change that will permit schema modification, and avoid sharing one highly privileged database user between unrelated applications.
01 Set database-user privileges in DirectAdmin
- Open MySQL Management and select the intended database.
- Find the database user and open Modify Privileges or its equivalent permissions control.
- Select the operations required for the task. A read-only reporting user normally needs a different set from an application installer that creates or alters tables.
- Save the change and update the application only if its connection identity is also changing. Do not grant every privilege simply to silence an error without identifying the failed operation.
- Test the workflow that needs the permission, including any legitimate upgrade or maintenance task. Remove temporary extra privileges after the approved operation when the application supports that arrangement.
02 Example: inspect the current connection grants
Connect as the database user whose permissions you are reviewing, then run:
SHOW GRANTS;Compare the database names and granted operations with the application's documented needs. Running this while signed in as a panel administrator shows that administrator's grants instead. Keep the output private because it can disclose account and authentication configuration. Treat it as inspection evidence, then test the required operation with the application identity; roles and server policy can affect the effective result.
How do I check the database user permissions?
Confirm the required action succeeds and that an operation intended to remain restricted is still denied. Review permissions on the actual application user rather than an administrator login in phpMyAdmin.
Resolve setup problems
If an application still fails, read its exact SQL error. A missing table, wrong database, unsupported SQL feature or connection failure is not necessarily a grant problem. Restore the recorded grants if a change breaks the application, then determine the minimum correct permissions. Ask support about restrictions outside your hosting-user scope.