> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elevatedsignals.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-tenant data segregation

> Why multi-tenant is valid for GMP, and how Invariant isolates your data.

Multi-tenant cloud is a **valid and widely adopted** architecture for regulated (GxP) operations — it
is the model used by the leading life-sciences eQMS platforms. Regulations (GMP, 21 CFR Part 11, EU
Annex 11) are technology-neutral: they require data integrity, access control, audit trails, and
demonstrable **logical segregation** — not a particular tenancy model.

## How Invariant isolates your data

* **Org-scoped access:** every query is scoped to the authenticated user's organization; the org is
  derived server-side from the session and cannot be spoofed by a client.
* **Database row-level-security (RLS) backstop:** even if application scoping were missed, the database
  itself filters rows by organization and rejects cross-tenant writes.
* **Tested:** a repeatable isolation proof demonstrates that same-org reads succeed while cross-org
  reads/writes are rejected at the database layer — this is provided as validation evidence.

## The continuous-release nuance

Unlike single-tenant on-prem, multi-tenant SaaS updates all customers together. Invariant addresses
this with a **release change-management process**: versioned release notes, change classification, and
per-release regression evidence, so you can perform a risk-based re-validation assessment. See the
Validation Accelerator Pack (artifacts A7 and A10).