Open the database → Users tab in my.cubepath.com.
Create dedicated users for your applications instead of sharing the admin account. It costs nothing and it's what makes access revocable: deleting one user cuts off one application, while rotating the admin password cuts off all of them at once.
Create a user
Click Create user and set the username. Leave the password field empty to have a secure one generated for you.
| Rule | Detail |
|---|---|
| Characters | Lowercase letters, digits and underscores |
| First character | Must be a letter |
| Length | Up to 32 characters |
| Reserved | System usernames (root, admin, postgres, …) are rejected |
| Password | 12–64 characters if you set your own |
WarningThe password is shown only once, right after creation, and cannot be retrieved afterwards. Copy it into your secrets manager or environment configuration before closing the dialog. If you lose it, delete the user and create it again.
Delete a user
Deleting removes the user from the database. Any application using those credentials loses access immediately, which is the point when you're revoking, and a surprise outage when you're tidying up.
TipBefore deleting a user you think is unused, check the Connections chart on the Metrics tab. A connection count that doesn't drop to zero when you stop the service you know about means something else is still connected.
A workable convention
- One user per application, named after it.
- A separate user for migrations from the one your app runs with, so day-to-day traffic doesn't hold schema-changing rights.
- Rotate by creating the new user first, switching the application over, then deleting the old one. That way there's no window where nothing can connect.