Skip to content

Login and row policies

A locked server knows its reader in one of these ways (options.auth):

Mode When
Auth proxy an existing SSO in front (oauth2-proxy, Pomerium, Cloudflare Access): trusted identity headers plus a shared secret
Built-in login users with passwords in a file, sessions by the server
OIDC sign-in with your identity provider (Entra ID, Okta, Keycloak, Google)
JWT bearer machine callers and apps with tokens from your issuer
API keys scripts, exports, ingest, previews — scoped to dashboards and variables
Signed embed links dashboards inside another app (Embedding)

The identity becomes claims (__claim_user, __claim_groups, __claim_<name>). A row and column policy (options.policy, JSON) rewrites every query: a table gets a row filter on the claims, columns are hidden or masked — for every panel, export and API alike. Without a policy a server with a login refuses to start unless told "policy": "none".

Details: login via a proxy, built-in login, policies, what remains the operator’s job.