The Client SQL access guide

Start with an invitation

Open the full invitation link. New users create a password; existing users verify their current password. The one-time invitation is bound to a workspace, role, and expiry.

Owners and administrators manage people. A member receives no database permissions until someone assigns them.

Grant only what is needed

Permissions lists one row per person or coding client. Open a row to see each grant, who created it, and revoke one at a time. Granting is also per person: choose the database, then select every data and migration permission they need in one step.

Reads can be scoped to a schema or table. A delegable grant allows the person to grant equal or narrower access to other members. Its descendants cannot outlive it. Revoking a grant removes inherited access too. Removing a member revokes their workspace sessions, clients, and relevant grants. Rejoining does not restore old permissions.

Connect a coding client

Each person may connect one Codex, one Cursor, and one Claude Code client. Open the connected slot to change tables, write policy, or replace the token. Creating a second client of the same tool is refused.

The token appears once. Keep it out of source control and shared screenshots. A workspace administrator can revoke one client without disabling the person's other clients.

Sessions and credentials

Browser sessions use a host-only HttpOnly cookie, with origin and CSRF checks for changes. Sessions persist between visits and end on their own window, which Settings reports for your account. Signing out, changing your password, or changing your authenticator revokes them. Production cookies require HTTPS.

Password changes and resets revoke previous browser sessions and coding-client tokens. The database password is encrypted on the server and is never returned to the browser or MCP client. Removing a connection hides it from the workspace and keeps the record so it can be restored later.

Protect your account with two-step verification

Production workspaces require an authenticator before database or coding-client access. Sign in with your password and a fresh authenticator code, or use one of your single-use recovery codes. A password reset does not remove this requirement.

Authenticator changes revoke previous browser sessions and coding-client tokens. Store recovery codes privately. They are shown once, and replacing them invalidates the previous set.

New passwords are checked against known breaches. Have I Been Pwned receives only a five-character hash prefix, never your password or its full hash. Password creation and changes wait if screening is unavailable.

Review migrations through Liquibase

Use the existing changelog or supported SQL file pairs. Preview keeps SQL, rollback evidence, the source commit, and a plan hash together. Production changes require an independent authorized reviewer, and the plan is rechecked before execution.

Schema migrations do not run through the ordinary query editor.

Reach a database that is not on the public internet

Create a private network, run the gateway on a host that already reaches that company's PostgreSQL, then choose the network when you add the connection. The gateway opens an outbound WebSocket. Nothing inbound is required.

Direct connections stay available when Client SQL can already route to the host, including an existing site-to-site path. Do not build a new VPN into the shared Cloud Run VPC for each customer.