Identity

Who it is for

Any team member or integrator needing one sign-in and programmatic access model.

What works today

• ·Supabase auth for console routes
• ·Org roles and delegated approvers
• ·zentro_sk_ API keys in Settings

Problem

Every product needs consistent sign-in, roles, and programmatic access — not one-off auth per feature.

Solution

Identity spans Supabase auth, organization members, delegated approvers, and zentro_sk_ API keys.

How it works

1. Supabase sessions protect console routes.
2. Org roles filter modules (including auditor workspace).
3. API keys and ingest tokens managed in Settings.

Benefits

• ·Single sign-in for all Platform modules
• ·Service role used only server-side for webhooks

Roadmap

• →Cross-product SSO documentation
• →Fine-grained product scopes on API keys