Multi-unit onboarding
One owner, multiple locations. Each location gets its own workspace.
For Hub admins
This is the same onboarding workflow you already run, just repeated per location and reusing one owner. Follow the standard onboarding workflow for each location, then assign the existing owner to every workspace.
Onboard a multi-unit owner
Create one workspace per location
Follow Onboard a new workspace for each location. Name workspaces clearly (Brand - City or Brand - Unit #) so the owner can pick the right one in the Switcher.
Assign the existing owner to each workspace
From Organization, then User Seats, open the owner's record and add every workspace they manage. They switch between locations using the Switcher in the top-left.
Connect socials per workspace
The owner switches into each workspace and connects that location's social accounts separately. Connections do not carry across workspaces.
Connect one workspace at a time
Do not switch mid-connection. It causes confusion about which account belongs to which location.
How multi-unit works
Once the owner is assigned to several workspaces, everything stays scoped to the location they are currently in. Use this reference to see what is shared versus per location.
| Feature | Behavior |
|---|---|
| Switcher | Shows every workspace the owner is assigned to |
| Posts | Per workspace, to that workspace's connected accounts |
| Playbooks | Opted into per workspace |
| Analytics | Scoped to the active workspace |
| Calendar | Shows the active workspace's content only |
Tips for multi-unit onboarding
Use consistent naming so locations are easy to scan: Brand - City or Brand - Unit # beats free-form names. Remember that budgets are per workspace, so each location has its own Stripe subscription.