Concepts
Tenants
A tenant is your isolated workspace. Templates, contacts, providers, API keys, audit log — all scoped per-tenant.
When to create multiple tenants
Most teams use a single tenant. Reasons to spin up more:
- Per environment — production, staging, dev. Avoids polluting prod templates with test data.
- Per brand — you operate two consumer apps from one company; each has its own sender IDs and templates.
- Per business unit — marketing team and engineering team need distinct API key sets.
Lifecycle
| State | Meaning |
|---|---|
active | Normal operation. API keys work, dashboard works. |
suspended | API keys 401 with tenant_suspended. Dashboard loads in read-only mode. Reversible. |
archived | Soft-deleted. 30-day retention then hard-deleted via cron. Undo available within the window. |
Roles within a tenant
HIERARCHY
Higher roles include all lower-role permissions.
owner ⊃ admin ⊃ member ⊃ viewer.| Role | Can do |
|---|---|
owner | Delete tenant, transfer ownership, all admin permissions |
admin | Manage API keys, providers, sender IDs, members, templates |
member | Send messages, view history, edit templates |
viewer | Read-only — see dashboards but not send or change anything |