For the bearer-token, M2M, and local development auth contract, see
Authentication.
What’s Isolated
| Resource | Isolation Level |
|---|---|
| Database | Separate storage per tenant |
| Tool registry | Per-tenant tool assignments and state |
| LLM config | Per-tenant model, temperature, token limits |
| Knowledge bases | Tenant-scoped documents and embeddings |
| Conversations | Tenant-scoped history |
How It Works
Tenant context is extracted from the configured Auth0 tenant claim, the validated M2M tenant claim plussnc-tenant header, or DEV_TENANT_NAME in
local bypass mode. The runtime uses that tenant to select the database, tool
assignments, knowledge bases, cached results, artifacts, prompt configuration,
and user memory for the request.
For a single-tenant deployment, every valid token resolves to the same tenant
database. For a multi-tenant deployment, each valid tenant key maps to a
separate tenant database.
Machine Tenant Context
Machine-token requests carry tenant context in two places:| Source | Requirement |
|---|---|
| Token tenant claim | Must exist and pass tenant-name validation. |
snc-tenant header | Must be present and match the token tenant claim. |
snc-userid header | Must be present for acting-user attribution. |
Tenant Provisioning
When a new tenant is first seen, AgentFlow automatically:- Creates the tenant’s storage
- Runs any necessary setup
- Initializes default agent configurations
Per-Tenant LLM Configuration
Each tenant can override default LLM settings:llm_config.
