Skip to content
Docs home

DEVELOPER · UPDATED AUGUST 2026

Authentication

Supabase auth for the product surfaces, OAuth providers for login, and bearer secrets for scheduled and provisioning endpoints.

Product authentication

The dashboard, account, and staff surfaces authenticate through Supabase: the browser bundle carries the publishable anon key (VITE_SUPABASE_PUBLISHABLE_KEY) and the server holds the service role key, which is never exposed to the client. Every protected server function runs an auth middleware that resolves the caller's session and role before any data is touched.

OAuth providers

Login supports Google and Microsoft through OAuth authorization-code flows, with dedicated callback routes that exchange the code, refresh tokens, and decode identity. Email login follows the standard reset-password flow. Passwords and tokens never appear in logs, error contexts, or evidence artifacts — they are members of the closed forbidden key set.

Service authentication

Non-human callers use bearer secrets rather than user sessions: cron endpoints require the cron secret header, the metrics endpoint requires the metrics token, the Alertmanager sink requires its webhook secret, and SCIM endpoints use a provisioning token. These secrets are environment-configured, rotated like any other credential, and logged only as presence checks — never as values.

Two keys, two jobs

The publishable key is public by design and can only do what row-level security allows. The service role key bypasses RLS and lives server-side only. If you see the service role key anywhere in a browser bundle, that is a deployment defect — fix it before anything else.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.