Multi-Tenancy

Organization Model

Every top-level resource is owned by an Organization. This allows a single deployment to serve multiple home care agencies with isolated data.

• Users, referrals, applications, forms, schedules, documents — all carry a foreign key to Organization.
• Organizations can carry custom branding: logo, favicon, and custom CSS served to the portals SPA.

Service Types

Beyond org isolation, each organization is also configured for one or more service types:

Service Type	Description
Home Care (HC)	Non-clinical personal care services
Home Health (HH)	Clinical / skilled care (Medicare/Medicaid regulated)

A client can be enrolled in HC only, HH only, or Both. This is the second axis of variation in the platform — it controls which modules are visible on the client profile, which document sets apply, and which regulatory requirements are active (e.g. OASIS Assessment is HH only).

Almost all 13 organizations offer both service types. Aurora Home Health (Minnesota) is the only exception — it is Home Health only and has no Applicants or Caregivers module.

See Client Profile & Navigation for the full module visibility matrix.

Tenant Isolation

• API endpoints filter querysets by the requesting user's organization automatically via DRF permissions / queryset scoping.
• MASTER role users can administer across organizations (platform-level).
• ADMIN users are scoped to their own organization only.

Adding a New Organization

1. Create an Organization instance (via admin or fixture).
2. Create a MASTER or ADMIN user attached to it.
3. Configure branding fields (optional).
4. Invite employees / clients via the portals UI.