Manage database accounts

Create an application accountCopy Anchor Link

1. Open the database and select Database accounts in its sidebar.
2. Enter an Account name, such as app_backend.
3. Select Add account and wait for the operation to finish.
4. Open Connection in the sidebar. Select the active account under Connection account, then choose Load connection details.
5. Update the application configuration with the generated credentials and verify a new connection.

New databases automatically receive a random app_ account and password during provisioning. Once provisioning completes, open Connection to retrieve those credentials. You can create additional accounts using the steps above. Existing databases without a customer account still require manual account creation.

Names must start with app_, followed by 1–55 lowercase letters, numbers, or underscores. Passwords are generated automatically.

Every account you create administers its database. Accounts share ownership so they can create, alter and drop tables, indexes, sequences, schemas and functions created by other accounts in that database, including imported objects. All accounts have the same database-management access; read-only accounts are not currently offered.

This access does not include PostgreSQL server administration: accounts cannot create other databases or login roles, become a superuser, change server-wide configuration, or use extensions that require superuser privileges.

Normal connections use a shared owner role. current_user shows that role; use session_user to identify the original login account. Avoid RESET ROLE or overriding the connection's role setting when creating objects: objects created under a personal login will not have shared ownership.

If an account cannot modify existing objects, contact support with the resource ID and displayed error. Creating another account does not resolve existing object-ownership issues.

Rotate an application passwordCopy Anchor Link

1. Select Rotate password for an active application account.
2. Confirm with Generate new password.
3. After completion, load the new connection credentials.
4. Update application secrets and reconnect clients.

The username stays the same. Existing sessions are not disconnected by rotation, so test a new connection to verify the replacement password.

If the Console reports an interrupted update, the database password might already have changed. Check operation status and reload credentials before retrying; do not assume the old password remains valid.

The Console does not expose password rotation for the initial administrator or deletion of application accounts.