Tenancy Customization

Every multi-tenant application answers the same question for each feature: does every tenant share the application's setting, or does each tenant set its own?

The Tenant Customization section under Application → Settings → General is where you make those decisions. Four switches:

┌──────────────────────────────┬──────────────────────┐
│ Branding                     │ Application │ Tenant │
│ Email Templates              │ Application │ Tenant │
│ Email Provider               │ Application │ Tenant │
│ Isolated Auth Stack          │   Shared    │ Isolated │
└──────────────────────────────┴──────────────────────┘

The first three are simple "shared vs per-tenant" toggles. The fourth is a deeper architectural decision — it controls whether tenants share one user pool and one auth surface, or get fully separate ones.

Where it lives#

Dashboard → Application → Settings → General → Tenant Customization. The section only appears for multi-tenant applications. Single-tenant apps don't show it (there's nothing to scope).

The "Application vs Per Tenant" pattern#

Each scope toggle has two values:

• Application (default) — there is one configuration for the whole application. Every tenant inherits it. The dashboard's Branding / Communications pages don't show a tenant picker; they edit the shared config.
• Per Tenant — each tenant has its own configuration. The dashboard adds a tenant picker at the top of the relevant page; switching tenants shows that tenant's overrides (or the inherited application defaults if the tenant hasn't customized).