Multi-Brand Workspace Isolation (Onboarding)

Multi-Brand Workspace Isolation (Onboarding)

1. 01

   Map every client brand to a single workspace before any content is loaded

   One workspace per brand keeps publishing permissions, inbox routing, and reporting scoped correctly. Platforms such as Sendible and Cloud Campaign are built around this separation, so a shared workspace forces manual filtering later.

2. 02

   Assign named owners for each workspace rather than a shared agency login

   Named seats make approval history and revision accountability traceable when a client disputes who signed off on a post.

3. 03

   Confirm which social profiles the client owns versus which the agency created

   Profile ownership determines who can reconnect a broken token and who holds the recovery email. Record the answer in the client file, not in a chat thread.

4. 04

   Set role permissions by function: publisher, approver, analyst, viewer

   Junior staff should draft without publish rights. Approval routing in Sked Social and Planable depends on these roles being defined before the first campaign, not after.

5. 05

   Load brand assets and tone rules into the workspace before the first draft

   Logo files, color values, banned phrases, and required disclaimers belong in the workspace so any team member can produce on-brand work without asking.

6. 06

   Test one scheduled post per connected channel and verify it publishes

   Channel APIs break silently. A single test post per network catches expired tokens and permission gaps while the client is still in onboarding, not during a launch week.

7. 07

   Document the workspace map in the client handoff file

   List workspace name, connected profiles, seat owners, and approval chain. This becomes the reference when the account moves between delivery teams.