Database access in Hepsia just became far more flexible. TrexHost has rolled out a fresh set of MySQL Database Manager enhancements—shaped directly by customer requests—that put precise control over database users into your hands.
The headline changes: you can now attach multiple users to a single database, assign each one its own permission set, and give temporary accounts an automatic expiry date.
The result? Easier collaboration with developers, teammates, and AI tools—without granting anyone more access than they actually need.
Here’s everything that’s new and how to put it to work.
A Database Can Now Have Several Users
In the past, Hepsia tied each database to one matching user account. It kept things tidy—no juggling usernames—but it forced everyone who needed entry to share identical credentials.
That’s no longer the case. Every database can now host multiple user accounts, each with a distinct password and its own permissions.
Consider a few practical scenarios:
- A developer gets write access to update records, all without seeing your primary database password.
- An AI assistant receives read-only rights, letting it pull information while being blocked from altering or erasing anything.
- A freelancer gets an account limited to precisely the operations their task requires.
Whenever multiple people or applications share a database but shouldn’t share the same level of control, this is the answer.
Automatic Expiry for Temporary Users
TrexHost has also built expiration dates into database user creation—a feature that quietly saves a lot of headaches.
Picture a contractor who needs database access for one week. Rather than trusting yourself to remember a cleanup task later, you assign an end date at account creation. When that day comes, Hepsia shuts the account’s access down on its own.
For users who should have ongoing access, just skip the expiration field entirely.
The upshot: no forgotten logins sitting active in your database months after they stopped being relevant.
Adding a New Database User
The workflow is quick and straightforward.
Inside Hepsia, open the MySQL Database Manager and locate the database you want to configure. In the Actions column, click the Add User icon.
You’ll be asked to fill in:
- Username — the identifier for the new account.
- Password — the credentials it will use.
- Permissions — the operations this user may carry out.
- Expiration date — optional; leave it empty for access that never lapses.
A few important details:
- After creation, the username is permanent—but passwords can be updated whenever needed.
- Expiration dates cannot be modified once set, so pick your date deliberately.
- Users default to no expiration unless you choose otherwise.
Permission Control, Down to the Operation
Creating separate users is only half the story. TrexHost now lets you dictate precisely what each account can do inside your database. Someone who only reviews data can be confined to read-only access; a developer can be granted the specific powers their work demands.
The main MySQL permissions you can assign:
| Permission | What it permits |
|---|---|
| SELECT | Reading data from tables |
| INSERT | Adding new records |
| UPDATE | Modifying existing records |
| DELETE | Removing records |
| CREATE | Creating tables and other database objects |
| DROP | Deleting tables and their contents |
| ALTER | Changing table structure (adding/removing columns, etc.) |
Permissions can be mixed and matched to fit the role. An AI agent doing lookups, for example, needs only SELECT—and gains no ability to change or delete data.
The guiding principle: every user gets what their job requires, and nothing beyond that.
Updating Permissions When Needs Change
Roles evolve, and permissions should be able to follow. From the MySQL Database Manager, locate the user and click the permissions link shown beneath their username.
Full-access accounts display “All privileges,” while limited accounts list their specific permissions. Click the link to inspect or adjust them whenever necessary.
A Word About Default Database Users
Your existing default users now show up in the MySQL Database Manager too. These accounts come with full permissions by default—deliberately, since your websites and applications rely on them to operate correctly.
TrexHost’s recommendation: don’t touch those defaults unless you’re confident about what your application requires. Removing permissions from, for instance, a WordPress site’s default database user can cause parts of the site to malfunction.
Need to give someone restricted access? Create a new, separate user for that purpose instead of altering the default account.
The Bigger Picture
These enhancements hand TrexHost customers a degree of database access control that used to demand workarounds or extra tooling. Dedicated accounts replace shared logins. Permissions match actual responsibilities. Temporary access disappears on schedule, without manual intervention.
If you collaborate with developers, oversee multiple websites, or run AI-powered tools against your data, these options make it simpler to keep databases organized—and safer by default.
Everything covered here is available now in the Hepsia Control Panel.
Try the new features and share your feedback. Customer input is exactly what shaped these improvements, and it’s what will continue to guide how TrexHost evolves Hepsia going forward.