How to manage databases in the control panel
Open your website in the hosting control panel, then select Databases. Database users are credentials that applications use to connect to a database. They are separate from your Kiravo login, contacts, and WordPress administrator accounts.
An empty website shows No databases or users, with Add database and Add user buttons.

Create a database (with a user)
Section titled “Create a database (with a user)”- Click Add database and check the usage and allowance shown above the form.
- Enter Database name. The fixed prefix shown beside the input is part of the final name. For example, if the prefix is
example_, enteringappdbproducesexample_appdb. - Click Create new user to reveal Username and Password. The username also includes the displayed prefix.
- Set a unique password, or use the key button to generate one. The form requires at least 10 characters, including a lowercase letter, an uppercase letter, a number, and a special character.
- Review All database privileges, which is selected by default. Clear it and review the available privileges if the account needs narrower access.
- Under Advanced, change Authentication plugin only if your application’s connection requirements call for it.
- Save the full database name, full username, and password in your password manager, then click Add. Use Cancel to abandon the form.

Check the resulting database and user after creation. Do not assume that entering names without their prefixes will work in your application.
See your databases and users
Section titled “See your databases and users”Once resources exist, use Databases and Users to switch between them. The database list identifies each database’s name, type, attached users, and size. The user list shows usernames, type, and linked databases.
Open a row’s management action to inspect the database or user. Check which databases a user can access and which privileges it has before sharing its credentials or connecting another application.
Add a standalone user
Section titled “Add a standalone user”Click Add user to open Add database user. Enter the username and password, and review Advanced if you need an authentication plugin. Click Add after saving the credentials.
Creating a standalone user does not by itself confirm access to a database. Return to the management controls and check its database assignments and privileges before using it in an application.
Connect your application
Section titled “Connect your application”Use the complete database name, complete username, database password, and database host provided for your website. Check Overview → At a glance for the database address. Do not substitute the public website domain or the control-panel address unless your connection details specifically require it.
Update the application’s database configuration, then test a page that reads data. If the connection fails, compare the full names, host, and privileges before changing passwords or creating another database.
Open phpMyAdmin
Section titled “Open phpMyAdmin”Use the phpMyAdmin action offered for the database, or the shortcut under Overview → Quick links. Check the selected database after the handoff. Access depends on the available database and your permissions.
phpMyAdmin lets you browse tables and import or export SQL data. Before an import, an update query, or a deletion, take a manual backup and confirm the target database. An SQL import may replace data already used by the live application.
Manage or delete a database
Section titled “Manage or delete a database”Open the database’s row menu and choose Manage to inspect its details and attached users. Use Delete only after checking the name and keeping the data you need.
Manage or delete a user
Section titled “Manage or delete a user”Open the user’s management action to review its database access. If you change a database password, update every application that uses it and test those connections afterward.
Deleting a user removes that account’s access. It does not replace the database credentials in your application’s configuration or delete the database itself.