WebHost4Life has unveiled a substantial update to the MySQL Database Manager inside Hepsia—and every change was driven by direct customer feedback. The goal is simple: give you precise, hands-on control over who reaches your databases and what they can do there.
What’s New at a Glance
- Several users can share one database — each with unique credentials
- Custom permission sets per account — access tailored to each role
- Optional expiry dates — temporary accounts deactivate automatically
The result is smoother collaboration with developers, team members, contractors, and AI-powered tools—without over-provisioning anyone’s access.
Multiple User Accounts per Database
In the past, Hepsia matched each database to a single user account. That kept things organized, but it meant everyone who needed entry worked from the same credentials and the same privileges.
Now that’s changed. A single database can support multiple user accounts, each with a separate password and its own permission profile. Some real-world examples:
- A developer can be given write access to update records—while never seeing your main database password.
- An AI assistant can be limited to read-only access, able to pull data but blocked from altering or deleting it.
- A freelancer can receive an account restricted to exactly the tasks their engagement covers.
If multiple people or applications need to use one database at different levels of trust, this is exactly the tool for the job.
Temporary Accounts With Built-In Expiration
WebHost4Life has also added expiration dates to the user-creation process—a quiet feature that eliminates a lot of future cleanup work.
Imagine a contractor who needs database access for just one week. Rather than counting on yourself to remember to revoke access later, you specify an end date when the account is created. On that date, Hepsia disables the account’s access automatically.
For accounts that should remain active indefinitely, just leave the expiration field empty.
The benefit: no forgotten credentials sitting active in your database long after the person or project has moved on.
Creating a New Database User
The workflow is fast and intuitive:
- In Hepsia, open the MySQL Database Manager and find the database you want to configure.
- In the Actions column, click the Add User icon.
- Complete the form:
- Username — the name identifying the new account
- Password — the credentials it will use
- Permissions — the operations this user is allowed to perform
- Expiration date — optional; leave blank for access that never expires
A few points to remember:
- The username can’t be changed after creation—but passwords can be updated at any time.
- Expiration dates are locked once set, so choose deliberately.
- Accounts default to no expiration unless you specify otherwise.
Operation-Level Permission Control
Creating separate users is only half the equation. WebHost4Life now lets you specify exactly what each account can do inside your database. A user who only reviews data can be restricted to read-only access; a developer can be given precisely the capabilities their work requires.
The key MySQL permissions you can assign:
| Permission | What it enables |
|---|---|
| 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 combined and tailored to fit any role. An AI agent doing lookups, for instance, needs only SELECT—and gains no ability to modify or remove data.
The core principle: each user receives what their job demands, and nothing beyond that.
Changing Permissions as Needs Evolve
Roles change over time, and permissions should be able to change with them. From the MySQL Database Manager, find the user and click the permissions link displayed beneath their username.
Full-access accounts show “All privileges,” while restricted accounts list their specific permissions. Click the link to review or adjust them whenever needed.
Important: Default Database Users
Your existing default users now also appear in the MySQL Database Manager. These accounts come with full permissions by default—deliberately, since your websites and applications rely on them to run correctly.
WebHost4Life’s recommendation: don’t modify those defaults unless you’re confident about what your application requires. Removing permissions from, for example, a WordPress site’s default database user can cause parts of the site to break.
Need to provide restricted access? Create a new, separate user for that purpose instead of altering the default account.
The Bigger Picture
These enhancements give WebHost4Life customers a level of database access control that used to require workarounds or extra tooling. Dedicated accounts replace shared logins. Permissions match real responsibilities. Temporary access expires on schedule, with no 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 WebHost4Life evolves Hepsia going forward.