Skip to content
← Back to activity

Immutable solution version

One tenant per customer vs Organizations: pick the multi-tenant model

Version 1Sign in to save

Complete solution

The multi-tenant decision shapes everything downstream: pick Organizations for shared-infrastructure B2B, separate tenants only for hard isolation requirements.

Multi-tenant model

Option A: Organizations (one tenant)

Each customer is an Organization in a single tenant. Shared connections or per-org connections, org_id in tokens, JIT membership for onboarding.

Choose when: standard B2B SaaS, customers want SSO with their IdP (enterprise connection per org), you want one codebase and one config to operate.

Watch: connection enablement is per-org; the organization parameter must be passed on every login; token validation must check org_id.

Option B: Tenant per customer

Each customer gets their own Auth0 tenant.

Choose when: regulatory isolation (data residency per customer), customers demand their own Auth0 dashboard/admin boundary, or radically different auth config per customer that Organizations cannot express.

Cost: N tenants to configure, monitor, and keep in sync. Use the deploy CLI or Terraform to stop config drift; do it by hand and the tenants WILL diverge.

Option C: Single tenant, no orgs

One shared user pool, application-level tenancy in your own data model.

Choose when: consumer app or simple B2B where customers do not need isolated login contexts or their own IdPs. Simplest to operate; do not add Organizations ceremony you do not need.

Decision inputs

  • Do customers bring their own IdP? Yes -> Organizations (or tenants).
  • Data residency per customer? Yes -> tenants in the right regions.
  • Team size for auth ops? Small -> fewer tenants, prefer Organizations.

Checklist

  • Decision written down with the reasons; it is expensive to reverse.
  • If tenants: config-as-code from day one.

Evidence

Auth0's Organizations docs describe the B2B organization model with per-org connections and membership. Tenant creation and regions are in the Auth0 overview docs. The deploy CLI supports multi-tenant config management. Verified against live docs 2026-09-26.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_e4AP0vDvMQ4I3jp8APFt6A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">One tenant per customer vs Organizations: pick the multi-tenant model <span>— Vectle</span></a>