Managing database access just got a whole lot smarter in Hepsia. TightHost has introduced a set of MySQL Database Manager upgrades built around one clear goal: letting you decide exactly who can touch your data—and for how long.
Until now, database access in Hepsia worked on a one-login-fits-all basis. That changes today. You can now spin up separate users for a single database, tailor what each one is allowed to do, and put a hard stop date on temporary access.
Here’s the full rundown.
One Database, Many Users
Previously, Hepsia paired every database with a single user account that carried the same name. Convenient? Yes. Flexible? Not so much—anyone who needed in had to borrow the same credentials.
That constraint is gone. Each database can now support multiple users, each with its own password and its own set of permissions.
A few ways teams are already putting this to work:
- Handing a contractor write access to specific records—without revealing your master database password.
- Spinning up a read-only account for an AI tool that needs to query data but should never alter it.
- Giving a teammate limited access scoped to exactly what their role requires.
The bottom line: shared databases no longer force shared logins.
Temporary Access That Expires on Its Own
TightHost has also added expiration dates to database user accounts—a small feature with outsized value for anyone who brings in outside help.
Say you hire a developer for a two-week project. Rather than relying on memory (or a calendar reminder) to revoke their access later, you simply set an end date when you create the account. When that date arrives, Hepsia cuts off their access automatically.
Need someone to have permanent access? Leave the expiration field blank and the account stays active indefinitely.
No more stale logins lingering in your database long after the project wrapped up.
Creating a New Database User
The process takes less than a minute:
- Open the MySQL Database Manager inside Hepsia.
- Locate the database you want to work with.
- Click the Add User icon in the Actions column.
A dialog will appear asking for four details:
- Username — what the new account will be called.
- Password — the credentials used to sign in.
- Permissions — the specific actions this user may perform.
- Expiration date — optional; leave blank for permanent access.
A couple of things to keep in mind:
- Usernames are locked once created—though passwords can be changed anytime.
- Expiration dates can’t be edited after the account is set up, so choose carefully.
- New users default to no expiration unless you specify one.
Fine-Tuning Permissions
Beyond separating users, TightHost now gives you surgical control over what each account can actually do. A staff member who only needs to pull reports? Read-only. A developer tasked with updates? Grant the specific rights they need—nothing more.
Here’s a quick reference for the main MySQL permissions available:
| Permission | Grants the ability to… |
|---|---|
| SELECT | Read data from tables |
| INSERT | Add new rows to a table |
| UPDATE | Modify existing records |
| DELETE | Remove rows from a table |
| CREATE | Build new tables and database objects |
| DROP | Delete tables and their contents |
| ALTER | Restructure tables (add/remove columns, etc.) |
Permissions can be combined freely. An AI lookup tool, for instance, typically only needs SELECT—giving it no path to modify or erase anything.
The principle is simple: give each user exactly the access their job demands, and not a permission more.
Adjusting Permissions Later
Needs change, and TightHost makes it easy to adapt. From the MySQL Database Manager, find the user in question and click the permissions link displayed beneath their username.
Accounts with unrestricted access will read “All privileges.” Restricted accounts will list their assigned permissions individually. Click through to review or revise them at any time.
A Note on Default Database Users
Your pre-existing default users now appear in the MySQL Database Manager as well. These accounts retain full permissions by default—which is intentional, since your sites and applications depend on them to function normally.
TightHost’s advice: leave those defaults alone unless you’re certain of your application’s requirements. Stripping permissions from, say, a WordPress site’s default database user can break core functionality in unexpected ways.
If you need to grant someone limited access, create a dedicated user for that purpose rather than modifying the default account.
Wrapping Up
These additions give TightHost customers a level of database access control that previously required workarounds or third-party tools. Separate accounts replace shared credentials. Permissions are scoped to actual need. Temporary access cleans itself up automatically.
Whether you’re collaborating with freelancers, running multiple sites, or wiring up AI-driven workflows, the new MySQL Database Manager makes it easier to stay organized—and safer by default.
Everything described here is live now in the Hepsia Control Panel. Take it for a spin and tell us what you think. Feedback from customers is what drives these improvements, and TightHost will keep refining Hepsia with that input in mind.
