Tenancy Design
Implement tenancy for your application built on Medplum.
Start with the Tenancy Design Decision Guide to decide whether you need multi-tenancy, what each tenant represents, what stays independent, and how people work across tenants.
Implementation sequence
| Step | Technical guide | What you configure |
|---|---|---|
| 1. Patient and clinical records | Patient Records and Clinical Sharing | One shared Patient per person or a separate Patient per tenant; clinical sharing and record lifecycle. |
| 2. Assignment and permissions | Tenant Assignment and Access | Resources representing tenants or finer groups, account assignments, and policy grants. |
| 3. Accounts and sessions | Identity, Memberships, and Sessions | One account with separate practice sessions, one account with access across practices, or independent practice accounts. |
For a separate project per tenant, start with Projects. This model requires self-hosting. Configure each project's required permissions, then plan accounts and sessions across projects.
Related foundations
Projects explains resource containers and project administration. Access Policies defines resource and field permissions; use the Access Control Decision Guide to choose them.
With or without tenants, UI filters can organize work using existing fields and relationships; tenant and care-team assignments in meta.compartment are optional. When care-team restrictions must apply at the API level, use matching policies. Within a tenant, combine practice and care-team restrictions when both are required.
Use Organizations and Locations to model your operating structure, and Authentication and User Management for sign-in and account provisioning.