The boundary
An organisation owns its members, its entitlement, its billing relationship, and every record any module holds on its behalf. There is no query anywhere in the product that returns a row belonging to another organisation, and tenancy is a required value with no default in every module that stores anything — a default is how a write lands silently in the wrong tenant, and silence is what makes that class of bug expensive.
Modules keep their own copy of your organisation, created the first time somebody from it opens the module and keyed on the shell's organisation id. That is why a module knows your company name without being told, and why a module you have never opened has nothing in it at all.
Switching
One account can belong to many organisations. The shell carries a switcher, and switching changes what every module shows, because modules read the current organisation from the same session.
- A session always has exactly one current organisation. At sign-in it is seeded from your oldest active membership.
- Entitlement is per organisation, so the rail can gain and lose modules as you switch. That is correct, not a fault.
- Switching does not sign you out of modules. It changes which tenant they answer for.
- A session with no current organisation cannot enter any module at all — the hand-off refuses it.
"I signed up and it threw me straight back out." Almost always an account with no organisation membership — created by hand rather than by invitation. The account can sign in to the shell and then bounces off every module. The fix is to add the membership, not to reset anything.
Switch organisation
Multi-entity is not multiple organisations
If you run several trading entities and want a group view, that is multi-entity consolidation inside one organisation — entities are a structure in Accounting, and consolidated reporting reads across them. Separate organisations are separate books with nothing between them, which is what you want for genuinely unrelated companies and an accountant's client list.
| You want | Use | Because |
|---|---|---|
| A group P&L across three subsidiaries | One organisation, multi-entity | Consolidation reads across entities, not across organisations. |
| Books for six unrelated clients | Six organisations | No client should be one query away from another. |
| A disposable test workspace | A second organisation | It is the closest thing to a sandbox. |
| Different branding per brand | One organisation, portal brands | The [Client Portal](/docs/modules/portal/clients-and-brands) handles brands inside one tenant. |
What this does not do
There is no supported path to fold one into another. Choose the structure before loading data.
By design. Consolidation is a within-organisation feature.
Deleting an organisation deletes module data across twelve applications, so it is a support operation.
Questions
How do I create a second organisation?
From the organisation switcher in the shell. You become its platform admin.
Can a module be enabled in one organisation and not another?
Yes. Entitlement is per organisation.
Does each organisation get its own bill?
Yes. Billing attaches to the organisation.