How to manage databases in the Kiravo control panel

The Databases section is where you create and manage the MySQL databases that power dynamic apps (WordPress, e-commerce, custom apps), along with the database users that connect to them. To open it, go to your website’s dashboard and click the Databases tab in the top menu bar.

If you haven’t created any databases yet, you’ll see an empty state with the note “Add databases with users that have different levels of access,” and two buttons: Add database and Add user.

Create a database (with a user)

The simplest way to create a database is to make both the database and its user in one step — a database needs at least one user to connect to it.

1. Click Add database. The form opens.
2. The top of the form shows your usage against your plan’s allowance (e.g. “0 of ∞ databases used” on an unlimited plan).
3. In Database name, type the unique part of the name. A fixed prefix tied to your account (for example, mynewsit1_) is added automatically, so appdb becomes mynewsit1_appdb.
4. Click Create new user to expand the user fields:
   • Username — type a username. It gets the same account prefix automatically.
   • Password — enter a password, or click the key icon to generate a strong one. Use the eye icon to reveal what you typed. The password must include one lowercase letter, one uppercase letter, one number, one special character, and be at least 10 characters long. A green “Password meets all requirements” message confirms when it’s valid.
   • Advanced → Authentication plugin — optionally choose the MySQL authentication plugin. Most users can leave this on the default; the info icon explains when you might need to change it.
   • All database privileges — a checkbox (ticked by default) that grants the user full access to the database. Leave it ticked unless you specifically need to restrict the user’s permissions.
5. Click Add to create both at once. A confirmation appears.

Note

Save the database name, username, and password somewhere safe. Your application needs all three to connect, and the password is generated/entered only once — you can’t view it again afterwards. If you lose it, you can reset it from the user’s ⋮ menu.

See your databases and users

After creating a database, the section shows two sub-tabs:

• Databases — every database, with columns for Name, Type (the engine, e.g. MySQL), Users (how many users are attached), and Size.
• Users — every database user, with Username, Type, and the Databases they’re linked to.

Switch between tabs with the toggles at the top. Add user and Add database stay available in the top-right corner.

Open phpMyAdmin

phpMyAdmin is the standard web UI for browsing tables and running SQL. On each database row in the Databases tab, there’s a phpMyAdmin icon (small orange/yellow). Click it to open phpMyAdmin in a new tab.

Inside phpMyAdmin you can browse tables, run SQL queries, import or export data (e.g. via .sql dumps), and manage the database’s contents directly.

Manage or delete a database

Click the ⋮ menu at the end of a database row to open its actions:

• Manage — open the database’s settings to view details and manage its attached users.
• Delete — permanently remove the database and everything in it.

Manage or delete a user

In the Users tab, the ⋮ menu on each user row offers the same shape of options:

• Manage — edit the user, including which databases it can access and its privileges.
• Delete — permanently remove the database user. The database itself is not deleted, but any app using this user to connect will lose access.

Add a standalone user

If you need an extra user for an existing database (for example, a read-only account for an analytics tool), click Add user at the top right. Fill in the username, password, and privileges in the same way described above, then save.

Caution

Deletions are permanent. Removing a database destroys every byte of data inside it. Removing a user breaks any app that connects with it. Always take a manual backup first, and grant only the access a user needs — if a user doesn’t require full control, untick “All database privileges” and assign narrower permissions instead.