By module

Administration

Enterprise controls: who can do what, how they sign in, how systems integrate — and the isolation and audit that make it all safe for regulated data.

Best use case

An admin standing up a workspace for a team: invite users, connect SSO, map directory groups to roles, and hand out scoped API/MCP access — all audited.

Roles & permissions

Access is granular resource:action permissions bundled into roles with data scopes(own → team → global), seeded per edition. Assign roles under Administration → Users / Roles.

Identity & SSO

Microsoft Entra and Google SSO with just-in-time provisioning; claim and verify your email domains (DNS TXT) to route SSO; provision users by pull (directory sync) or push (SCIM 2.0); connect a custom workspace domain and branded email.

Integration surfaces

API keys — scoped read or read+write bearer keys for the REST API v1.
Webhooks — subscribe to events (e.g. policy.bound), HMAC-signed and retried.
MCP — a per-workspace token so Claude or any MCP agent can act, tenant-scoped and audited.

Isolation & audit

Every workspace is isolated at the database with Postgres row-level security, and every change is written to an immutable audit trail. A cross-tenant operator console (for platform staff) manages workspaces.

Best practice

Prefer SSO + directory-group→role mapping over manual invites at scale; scope API keys to read-only unless a system genuinely needs to write.

Security overview · Documentation overview