Managing Sub Organizations
Table of Contents
Creating or Adding a Sub-Organization
- Click on the Add Organization button located to the right of the search bar.
- Choose either Create New Sub-Organization or Select from Existing Organizations.
- If selecting Existing Organization, a dropdown menu will appear.
- From the dropdown, select the desired organization. When creating a sub-organization, you can now copy settings for Call Routing and Care Plans from the parent organization. This saves time and ensures the sub-organization is set up the same way as the parent organization.
Nested Sub Structure
While a Hub Org can have multiple Sub Orgs underneath it, a Sub Org can only have one Hub directly owning it. However, Hubs can be arranged in layers with a Hub owning a Sub that is in itself a Hub of other organizations. In these cases, templates need to be shared down across the layers from the topmost Hub through the Intermediary Hub, to the Nested Sub organization.
Managing Members Across Sub-Organizations
- From within the Hub Control page, go to the Members tab in the top menu bar.
- Select Members to view the list.
- To control access, use the Assign Access Based on Specific Member panel or the Assign Bulk Access Based on Groups panel.
- Choose whether to Share or Don’t Share access with specific sub-organizations.
Managing Templates and Objects Across Sub-Organizations
- From within the Hub Control page, navigate to any Templates or objects tab (other than Members).
- Select the item you want to control access for.
- For each organization, choose the access type: Read, Write, or No Access.
- Customize access permissions by organization as needed.
💡 Object Types
Objects include Questions, Calculation, Domains, Groups, and Tags.
Access Types
| Access Type | Access Behavior |
| Write | The object is visible AND editable. Modifications made in the Hub org (where Write access originates from) or ANY of the other orgs with Write access will propagate across ALL instances of that object. |
| Read |
The object will be visible and usable in the sub org, but cannot be edited. EXCEPTION: Read access activity templates can have customized billing defaults set at the sub-org level for greater customizability and improved user experience. |
| No Access | The object will not appear in the sub org. |
Access Management
Write access to objects should be given sparingly in order to maintain the integrity of your build. Read access is advised wherever possible.
If a sub-organization has Read access to an activity template, in the Builder view of the object, they will see a message like: “You are unable to edit this template. Check with the Admin of the parent organization to grant you write access.”