The request
“A multi-tenant CRM schema with Tenant, User, Contact, Lead, Deal, and Activity tables. Users, contacts, leads, deals and activities belong to a tenant, and leads, deals and activities can be assigned to users.”
Then tryAdd a pipeline table for deal stagesAdd tags for contacts and leads
What is in this drawing
Read the decisions behind it.
01
All tables include a tenant_id FK to Tenant to enforce data isolation at the application level.
02
Users, contacts, leads, deals, and activities are scoped per tenant.
03
Relationships are defined with mandatory foreign keys and many-to-one cardinalities.
Use this pattern when building a multi-tenant SaaS application where simplicity and resource efficiency outweigh strict physical data isolation, and row-level security is managed in the application layer.
More like this