An additional database user lets you give a separate application or operator its own credential. This makes access easier to limit and revoke without changing every application that uses the database.
IN THIS ARTICLE
Check access and requirements
Identify the intended database and the required privileges. Choose a descriptive username, prepare a unique password and check whether the application connects locally or from an explicitly permitted remote host. Avoid a shared administrator credential.
01 Create an additional database user in DirectAdmin
- Open MySQL Management and select the target database.
- In its user section, choose Create New User or the available add-user action.
- Enter the username and generated password. Review the complete account-prefixed name shown in the result; the short name alone may not authenticate.
- Assign the user to the intended database and review its privileges. Do not assume the initial grant set is appropriate for a read-only report or a restricted integration.
- Configure the new credential in the application and test it before removing any old user. Store the secret in the application supported configuration mechanism and your approved credential manager.
How do I test the additional database user?
Test a fresh connection and the intended read/write workflow with this specific user. Confirm it cannot access unrelated databases. If replacing a shared credential, verify all dependencies before revoking the old one.
Resolve setup problems
If the user cannot connect, check the full name, password, host matching and database assignment. If the name is already taken, determine whether that user is intentionally shared before editing it. Do not enable unrestricted remote access as a shortcut. Report the sanitized connection error to support when host-level restrictions are unclear.