Org Hierarchy
PurpletGo supports a two-level organization hierarchy: one parent organization, and any number of child organizations underneath it. It's built for enterprise customers managing multiple business units or - for HR service providers - multiple client accounts from a single login. The hierarchy is one level deep: a child org can't have children of its own.
Org Hierarchy is available on the Enterprise plan. Every route in this feature is restricted to the Super Admin role of the parent org (or a custom role explicitly granted org_hierarchy_manage).
Creating a child org
Open Org Hierarchy settings
Navigate to Settings → Organization → Org Hierarchy. Only a superadmin of a root org (one with no parent of its own) can create children.
Name it and create
Give the new org a name (up to 120 characters) and create it. That's the entire form - there's no slug, invite-by-email step, or data residency selection. Creating the child org also adds you as a superadmin member of it, so you can switch into it right away and configure it like any other PurpletGo org.
You can also attach an existing, standalone PurpletGo org as a child, as long as you're already its superadmin and it isn't already part of another hierarchy.
Plan inheritance
Child orgs don't carry their own subscription - they inherit the parent's plan and feature set automatically. Employee/offboarding data for each child is still fully isolated at the database level; inheritance only affects which features are unlocked.
Shared checklist templates
A parent org can publish one of its checklist templates to all of its children. Once shared, each child gets its own independent copy of that template (including its items) the first time it's shared - it isn't a live, editable-in-place shared resource, so later edits to the parent's template aren't retroactively pushed to children that already received a copy. Unsharing just stops new children from getting a copy; it doesn't remove copies already made.
Consolidated view
From the parent org, a superadmin can pull:
- Consolidated stats - offboarding counts, employee counts, SLA breaches, and separation-type breakdowns, aggregated across the parent and all of its children
- Consolidated audit log - a merged, paginated view of audit log entries across the whole hierarchy, optionally filtered to one child org or by action
Both of these are read-only rollups; they don't let a parent admin act on a child org's individual records.
Removing a child org
Detaching a child (via Settings → Organization → Org Hierarchy) sets its parent_org_id back to null. The org, its employees, its offboarding history, and everything else about it are left completely intact - it just stops being part of the hierarchy and becomes a standalone org again. There is currently no way to hard-delete a child org's data through this feature, and no confirmation-text or re-authentication step, since nothing destructive actually happens here.