Members and access

Workspace administrators manage people, roles, invitations, and credentials. Resource permissions still apply inside a workspace; choosing a workspace does not grant access to everything in it.

The catalog and storage boundaries explain why a visible catalog resource or a physical Iceberg namespace is not itself a read grant.

People and roles

Invite a member through workspace administration and assign the smallest role that lets them complete their work. Review resource grants for domains and governed reads separately. An administrator can change membership, but table data still follows its contract.

Credentials for automation

Personal access tokens (gpat_) authenticate human automation over the tenant REST API and need a tenant UUID header because the token carries no tenant claim. Session JWTs carry their workspace claim. Agent keys (gak_) belong at the MCP edge and are not REST credentials. Issue a credential for the intended principal and record its expiration. Server-side session revocation and persistent denial after logout are implemented in the auth feature source, but have not been verified against the live local deployment in this documentation pass; confirm your deployment's version before relying on immediate revocation. Sending a workspace context is routing, not permission.

For the external request pattern, follow Call the public API. Operator administration is a distinct privileged surface and is not included in the tenant API reference.