Check the application’s database requirements and expected connection host. Decide the required privileges and keep database credentials outside publicly accessible files wherever the application supports that design.

1. Open Hosting Features > MySQL > Databases and add a database with a clear suffix. Avoid periods in its name.
2. Use the Create User option or create a user under MySQL > Users. Generate a unique strong password and store it securely.
3. Open the database’s person action to associate the intended user. Grant the privileges required by the application rather than using a shared administrative identity.
4. Set When Connecting From to the actual allowed connection source where supported. Review the default wildcard rather than accepting it without understanding the deployment.
5. Enter the full database and user names, host and password in the application’s protected configuration. Run its connection and installation checks.

The application should connect and perform its intended read/write operations. Confirm it is using the new database and does not have unintended access to another application’s data.

An access-denied error can indicate the wrong full username, password, host match or missing database association. Do not grant every remote host access merely to bypass a connection error; server networking and firewall policy are separate.

They can in some configurations, but separate users reduce the impact of a leaked credential and make password rotation or application removal easier to manage.

• Changing a SiteWorx database-user password
• Opening phpMyAdmin from SiteWorx for the correct database
• Scheduling SiteWorx backups with retention
• Changing SiteWorx file permissions for a specific application

• InterWorx: Database Guide
• InterWorx: Add Edit Delete MySQL Users