A database and a database user are separate objects. An application needs both a database to store data and credentials authorised to access it.
Create and connect
- Open Database Wizard or Manage My Databases and choose a clear project-specific name.
- Record the complete name shown by cPanel, including any account prefix.
- Create a dedicated user with a unique password saved privately.
- Add that user to the intended database and grant the privileges the application requires. Separate runtime and migration permissions where the deployment supports it.
- Enter the supplied host, database and username into the application’s private configuration.
- Run the supported connection or migration check and verify a normal application operation.
Avoid shared credentials
Using one user for every project increases the impact of a leaked password. Do not use a database administrator account for a public website’s routine requests. Keep configuration outside the public root wherever the framework allows.
Changing a database user password can immediately break every application using it. Inventory consumers first and deploy the configuration change together. Never publish a database export as a convenient download link. Use the hosting provider’s support process if the correct host or permission set is unclear.
Official references
Reviewed 2026-10-22. Menus and availability depend on your hosting plan and server configuration.
