Sub-Organizations
A sub-organization is a child organization nested under yours. It has its own users,
resources and configuration, while remaining under the parent's administration.
They suit arrangements where one group administers several distinct tenants — a health system
with separately-operated facilities, or a vendor managing an environment per customer.
Requesting one
Sub-organizations are not self-service. Go to Organization → Sub Orgs and select
Request Sub Organization; Intely provisions it and it then appears in your list by name.
Viewing this page requires organization-management permissions, so it is visible only to
administrators.
Users
A user can be created directly in a child organization, or synced down from the parent.
A synced user is administered at the parent and shows as synced in the child's user list —
change their access at the parent and it applies in the child.
This is the mechanism for giving your own staff access across every child organization without
maintaining a separate account in each one.
What is and isn't shared
Each sub-organization keeps its own integrations, mappings, app instances, files and logs.
Nothing is shared implicitly. Treat a child as a separate working environment that happens to
be administered from one place.
Updated about 6 hours ago
