> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spitshake.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tenant and partner model

> Understand standalone tenants, partner-managed firms, ownership, and billing boundaries.

Each SpitShake account is an isolated tenant. Users, API tokens, templates, submissions, signing
data, settings, and audit events belong to exactly one account.

## Standalone tenants

A standalone tenant signs up or is created through the ordinary account workflow. It manages its
own users, API credentials, and subscription through the tenant API and dashboard.

## Partner-managed tenants

A platform partner can provision new tenant accounts through `/api/partner/v1`. The resulting
firm is still a full isolated tenant, but the partner owns its plan and billing relationship.
Direct checkout and subscription creation return `403` for these accounts.

Partner keys are control-plane credentials and cannot access tenant resources. Provisioning
returns a separate tenant API token for resource operations. Likewise, tenant tokens, OAuth
tokens, and browser sessions cannot access the Partner API.

Partners may assign an `external_id` for stable correlation. It is unique within that partner.
Accounts cannot be moved between partners through the API, and an existing standalone account
cannot be linked or claimed. Firms bringing their own account remain standalone.

## Lifecycle

Suspending a partner blocks only partner-control-plane calls; existing firm tokens remain valid.
Offboarding converts every managed firm to a standalone free account and records the transition
in each firm's audit log before removing the partner relationship.