Organisation Hierarchy

A parent organisation can have any number of sub-organisations underneath it. It's built for enterprise customers with several business units and for HR service providers managing client accounts from one login. The hierarchy is one level deep: a sub-org can't have sub-orgs of its own.

Opened from inside a sub-org, the Org Hierarchy page tells you which parent the sub-org belongs to; the hierarchy itself is only managed from the parent.

Creating a sub-organisation

You can also Attach Existing to add a standalone PurpletGo org as a sub-org, if:

• you're a Super Admin of it
• it isn't already part of another hierarchy and has no sub-orgs of its own
• it has no active subscription (cancel it first, since the sub-org will use the parent's plan)
• it isn't scheduled for deletion

Plan inheritance

Sub-orgs don't have their own subscription. They use the parent's plan, trial, and read-only state, which is why every sub-org shows the parent's plan with (inherited). Each sub-org's data is still fully separate at the database level; inheritance only decides which features are unlocked.

If the parent's plan ends, its sub-orgs become read-only too.

Shared checklist templates

On the Shared Templates tab, share one of the parent's checklist templates with every sub-org. Each sub-org gets its own copy of the template and its items:

• existing sub-orgs get a copy when you share it
• sub-orgs created or attached later get a copy when they join
• a sub-org never gets a second copy of the same template

Copies stay linked to the parent's template:

• Editing the parent's template (its name or its tasks) updates every sub-org copy that the sub-org has not changed. A sub-org that never had a copy gets one
• A copy the sub-org changed is left as it is. Its Checklist Templates list in Settings shows Update available when the parent's template has changed since, with Re-sync to replace the copy with the parent's current version (the sub-org's own changes are then lost)
• Unshare stops new sub-orgs from getting a copy, removes the copies that sub-orgs never changed, and keeps the changed ones as the sub-org's own templates, no longer linked. A copy a sub-org uses in a role template or an automation rule is kept the same way, so they don't lose their checklist

Task keys (the tasks that follow their records, such as the exit interview task) are kept in every copy.

Consolidated view

The Overview tab shows totals across the parent and all its sub-orgs: sub-orgs, members, employees, active offboardings (not yet completed), completed offboardings, and SLA breaches. Below that are the list of sub-orgs and a chart of active offboardings per sub-org.

Switch into opens a sub-org. It's only offered for sub-orgs you're a member of; for the others, ask one of that sub-org's Super Admins to invite you.

The Consolidated Audit tab merges the audit logs of the parent and every sub-org, newest first, and can be filtered by organisation or action. It pages up to 10,000 events deep; filter to reach older ones.

This is a read-only rollup. It doesn't let a parent admin act on a sub-org's records.

Detaching a sub-organisation

Click Detach next to a sub-org. It becomes a standalone organisation. Its data, members, and history are kept.

Detaching never deletes data. To delete a sub-org, switch into it and delete it from its own Settings.

Deleting the parent organisation

An organisation with sub-orgs can't be scheduled for deletion. Detach its sub-orgs first. If a parent is deleted another way (for example after 12 months read-only), its sub-orgs are detached first, each with its own 14-day trial, and their data is kept.

Audit

Creating, attaching, and detaching a sub-org is recorded in the audit log of the parent and of the sub-org. Sharing, unsharing and pushing an edit to the sub-orgs' copies are recorded in the parent's log; a sub-org re-syncing its copy is recorded in the sub-org's log.

Related

• Security
• Compliance
• Reports