SaaS Multi-Tenant Database Schema

What this template is for

This SaaS multi-tenant database schema gives you a ready-to-edit ER diagram for any B2B SaaS where each customer (tenant) has isolated data. It models the entities every multi-tenant app needs: the Tenant itself, Plans and Subscriptions that drive billing, Users (a single global identity), Memberships that map users to tenants with a role, Workspaces inside a tenant, and the business Resource rows that all carry a tenant_id for row-level isolation. The key design decision is whether to use shared schema with a tenant_id column (most common) or schema-per-tenant — this template shows the shared-schema pattern. Use it to design a new SaaS, document tenant isolation for a security review, or explain how users join multiple tenants.

When to use this template

• Design the database for a new B2B SaaS where customers can't see each other's data.
• Decide between shared schema with tenant_id versus schema-per-tenant isolation.
• Model how a single user account can belong to multiple tenants with different roles.
• Plan billing entities: how subscriptions and plans relate to tenants.
• Document tenant isolation boundaries for a security or compliance review.
• Show where every business resource carries tenant_id for row-level filtering.

How to use it

1. 1Start with Tenant at the center — every other table either describes it or scopes to it.
2. 2Add Plan and Subscription so each tenant has a current plan and billing state.
3. 3Add User as a global identity and Membership as the tenant-user-role link.
4. 4Add Workspace inside a tenant (optional, for projects or teams within a tenant).
5. 5Add the business Resource tables; every one carries tenant_id for isolation.
6. 6Add an AuditLog scoped by tenant for compliance and debugging.

Quick example