Accounts and Organizations
How the top-level entities are structured and when to use a single account vs multiple organizations.
The operational problem
Multi-site operators rarely have one shape. A 3PL might run three distribution centers under one brand and a fourth as a separate joint venture. A QSR group might own three franchise concepts that share back-office staff but never share rosters. Force everyone into one shared workspace and the data tangles; force them into separate accounts and the rollups disappear.
How Array HQ solves it
Two layers, used together:
- An account is the contract — billing, data ownership, the legal boundary.
- An organization is a workspace inside the account. Each organization has its own roster, jobs, goals, rewards catalog, and members.
One account can hold many organizations. Members can have access to one or several, with different roles in each.
How it works
When to use a single account with one organization
Most customers. One brand, one operating reality, shared roster and reporting.
When to use multiple organizations under one account
- Multiple brands sharing a corporate team (regional VPs, central recruiting, central HR).
- A franchise group with distinct concepts that should not share roster data.
- A regional split where each region runs goals and rewards independently but rolls up to a single P&L.
Cross-organization rollups are available to Owners and Admins with access to more than one organization.
When to use multiple accounts
- A joint venture or partial-ownership business that legally owns its own data.
- An acquisition that's being kept on a separate billing relationship.
Multiple accounts do not roll up — that's the boundary.
What you'll be able to do
- Stand up a second organization in minutes when you launch a new brand or region.
- Give a regional VP visibility across three organizations while site managers see only theirs.
- Keep an acquired business on its own billing while still using Array HQ from day one.
Key terms
| Term | Meaning |
|---|---|
| Account | Top-level entity that owns billing and data. |
| Organization | A workspace inside an account. |
| Cross-org rollup | A view that aggregates data across multiple organizations within one account. |