Multi-Tenancy
How AuthSpoke isolates tenants — enforced server-side on every request, query and event.
AuthSpoke is multi-tenant. Isolation is enforced server-side throughout — never relied upon in the client.
Tenant context comes from your token#
Your JWT encodes a tenant. Tenant-scoped endpoints derive the tenant from the token and constrain every query to it. You don't pass a tenant id for your own data, and you can't read another tenant's data with your token.
What isolation guarantees#
- Every tenant-scoped query filters by tenant id.
- Every event, agent, MCP server and entitlement belongs to a tenant.
- A resource that exists in another tenant returns
404, not403— AuthSpoke never confirms the existence of data outside your tenant.
Cross-tenant operations#
The only cross-tenant surface is the Provider API, restricted to AuthSpoke provider admins by an allowlist. Provider operations explicitly take a tenantId and are audited.
Building multi-tenant integrations#
If your integration acts on behalf of multiple tenants, hold a token per tenant — do not attempt to share a token across tenants. Each token is the unit of tenant scope.