How to Configure PlanetScale Revoke Access

Published
Length
3 min read

Luis Felipe Dias

All posts

To perform a planetscale revoke access task, delete active branch passwords or remove user roles. You can also delete service tokens to block app connections right away. Engineering teams often create shared credentials so developers can fix production issues fast. Over time, these shared keys give too many people broad read and write powers. When someone leaves the team, rotating those shared database keys can break running apps. How the native planetscale revoke access workflow works Planet

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To perform a planetscale revoke access task, delete active branch passwords or remove user roles. You can also delete service tokens to block app connections right away. Engineering teams often create shared credentials so developers can fix production issues fast. Over time, these shared keys give too many people broad read and write powers. When someone leaves the team, rotating those shared database keys can break running apps.

How the native planetscale revoke access workflow works

PlanetScale manages database entry through three main layers. These layers are workspace member roles, service tokens, and branch passwords. When a person leaves your team, you first remove their user account from the workspace. This step stops them from logging into the web console or using the command line.

Removing a user does not kill database passwords they created earlier. Those strings still work until an admin deletes them. To cut off direct database connections, you must find and delete the specific branch password. Each branch has its own set of credentials with specific read or write roles.

Automated apps and scripts usually log in with service tokens instead of user accounts. You can cancel a service token or remove its branch rules at any time. Once you delete a password or token, the platform blocks new login attempts with that key. You should check all branches to make sure no spare keys remain active.

What native revocation solves and what it leaves open

Native password deletion works well when you give each app a single, dedicated key. You can delete one compromised credential without hurting other services that run on the same branch. Workspace role removal also keeps former staff from making new keys or reading branch data.

The main gap appears when human engineers need temporary access to live production branches. Giving an engineer a branch password grants broad power for as long as that password exists. Native roles decide who can log in, not what individual queries do in flight. A user with a valid reader password can still pull full tables of customer data.

Customer Support Access to Production: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

If several developers share one password for debugging, revoking it breaks everyone's work at once. Teams also have to remember to delete temporary passwords after an incident ends. Forgotten credentials often sit active for months with full read or write power. Even with strict password habits, raw queries can still return sensitive emails, phone numbers, or card numbers.

Managing temporary database sessions and active connections

Deleting a password stops new logins right away, but open sessions might stay active briefly. Admins must plan credential rotation carefully so live web apps do not drop user traffic. The safest method is to create a new password first and update your app settings.

Once the app uses the new key, you can delete the old password safely. For human users, teams should avoid static branch passwords whenever possible. Short sessions and query checks reduce the risk of leaked keys and broad data exposure. When you tie every query to an individual user, you no longer need shared passwords. You also gain a clear log of every command run against your production tables.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Does removing a team member delete their database passwords?

No, removing a user only blocks their console and command line login. Any branch passwords they made stay active until an admin deletes those keys.

How fast does deleting a branch password stop access?

Deleting a branch password blocks new database connections right away. You should still rotate app keys first so live services do not fail.

How can we limit what data engineers read during a session?

Native branch roles only split permissions between broad read and write levels. To rewrite sensitive fields like emails or card numbers in results, you need query-level data masking.

The query runs. The emails stay hidden.