Organizations

Admin → Organizations. The tenants. Same grid-plus-editor pattern as Users — a server-side DataTables list and a validated /api editor, with row controls gated by your ACL.

What an org is

• The tenant boundary. Every domain record belongs to an org; what stops a user acting across tenants is the absence of a membership linking them to that org — cross-tenant denial is structural, not a code check.
• Hierarchical. Orgs are self-referential (parent_org_id), so you can model sub-tenants / org trees.
• Extended by modules, not by columns. The Account module adds org detail via its own FK-linked tables — Tiger never adds columns to the core org table, so the platform can update without breaking your extensions.

Memberships

A user joins an org through a membership (org_user) that carries their role in that org. Managing who's in an org — and at what role — is membership management; see Users and Multi-tenancy.