Multi-Tenancy

Clarix is a multi-tenant platform where each organization (503B pharmacy) operates in complete data isolation.

Data Model

Every domain table includes an organization_id foreign key. All queries are scoped to the user's active organization.

User <Icon name="ArrowRight" size={12} /> belongs to <Icon name="ArrowRight" size={12} /> Organization
Organization <Icon name="ArrowRight" size={12} /> contains <Icon name="ArrowRight" size={12} /> Batches, Inventory, Equipment, etc.
Session <Icon name="ArrowRight" size={12} /> has <Icon name="ArrowRight" size={12} /> active_organization_id

Current Implementation

Organization Entity

Each organization stores:

• Name and slug (URL-friendly identifier)
• License number (state pharmacy license)
• DEA number (Drug Enforcement Administration)
• Settings (JSONB — timezone, feature flags, branding)
• Address and contact information

Future: Membership Table

The roadmap includes an organization_member table that will:

• Allow users to belong to multiple organizations
• Store role per-organization (not globally on user)
• Enable invitation/accept flows
• Support org switching in the UI

Isolation Guarantees

1. App-level scoping — Middleware injects organization_id from session
2. FK constraints — All domain tables reference organization.id
3. Planned RLS — Postgres Row-Level Security as defense-in-depth