On this page

Tenancy Design

Implement tenancy for your application built on Medplum.

Choosing your tenancy design?

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​

StepTechnical guideWhat you configure
1. Patient and clinical recordsPatient Records and Clinical SharingOne shared Patient per person or a separate Patient per tenant; clinical sharing and record lifecycle.
2. Assignment and permissionsTenant Assignment and AccessResources representing tenants or finer groups, account assignments, and policy grants.
3. Accounts and sessionsIdentity, Memberships, and SessionsOne 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.

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.