Tenant isolation prevents one customer’s private rows from appearing in another customer’s queries. In a shared-table design, the application—not the database—must enforce that boundary by applying the correct tenant predicate to every query. section 7.4
The missing predicate
A query scoped with `WHERE teamId = ?` stays inside one tenant. Omitting that condition can return another tenant’s rows because a shared database does not enforce isolation automatically. Nested ownership makes the check sharper: queries may need to verify both a team identifier and an organization identifier. section 7.4
Evaluate the isolation boundary by asking:
- Does every application query carry the correct user, team, or organization scope? section 7.4



