Organizations
An organization is a firm. It is also the boundary that every other feature in this platform is written against, which is why it gets its own page this early.
What belongs to an organization
Effectively everything: records and their revisions, content types and their fields, vocabularies and terms, files and their folders, menus, listings, appearance, mail servers and signatures, form submissions, redirects, and the permissions that govern all of it.
Nothing is shared by accident
Two firms on one installation that happen to hold the same file, byte for byte, are still two stored files. Deduplication is keyed on the organization together with the content — never the content alone. Sharing the byte would have been cheaper and would have been a leak.
What an organization does not change
The address of a page, the shape of a content type and the rules of the platform are the platform's. An organization decides whose data you are looking at, not how the system behaves.
Sites and organizations
A website belongs to an organization through a site. A site knows its host names, so a visitor arriving at one firm's domain sees that firm's content and nothing else — the public channel is always exactly one firm.
| You have | You get |
|---|---|
| One firm, one domain | The simple case; nothing to configure |
| One firm, several domains | Several sites, one organization |
| Several firms | Several organizations, each with its own sites, users and data |
Switching
Use the toolbar. Switching changes what every listing, form and page in the channel is about — it is not a filter, it is where you are.
A cross-organization reference resolves to nothing
If a record somehow points at another firm's record, the link resolves to silence — the same silence an unpublished target gets. It does not show a label, and it does not show a broken link. A leaked label is still a leak.