Organisation trees
An organisation can have a parent, and there is no limit on depth: a franchise with regions and branches, or a reseller with clients of its own. Depth is not a setting and is not tied to a plan.
Reading down, writing in place
A caller standing in an organisation reads its own rows, the rows of every organisation beneath it, and the rows shared across the project. It creates, changes and deletes only its own. A membership works the same way, reaching every organisation below the one it names and none above or beside it.
Definitions inherit from above
What you define at the project is inherited by every organisation, and what an organisation defines is inherited by those beneath it. That covers models, operations, locales, context dimensions, sign-in providers, design tokens, notification categories and variant catalogue entries. Where two levels define the same thing, the deepest one wins, so a branch can extend what its region set up.
Moving, suspending and deleting
Moving an organisation moves everything beneath it, and no key, session or membership is revoked. Suspending one covers its subtree without rewriting any rows. Deleting one schedules it and everything beneath it on a 30-day window.
Placement the database refuses
An organisation cannot be placed under itself, under one of its own descendants, or under a parent in another project. Those rules are enforced by the database, whichever route the change arrives by.
Read the detail
The trees guide sets out what each kind of caller reads and writes at every level, and which definitions inherit.