Overview
StretchSocial is built for teams that manage social for more than one brand or client. Because every record — connections, posts, queue jobs, analytics — is scoped to your organization, and because you can register multiple connections and organize work by campaign, a single workspace can cleanly run several brands with client sign-off built in. This guide is the playbook.
Set up each brand's channels
1. Open Connections and add a connection for every account you manage, using brand-prefixed labels so accounts never get confused:
- Brand A LinkedIn, Brand A Instagram
- Brand B LinkedIn, Brand B X
2. You can register several connections on the same network (two LinkedIn Pages, for example) — each is its own card with its own status and handle.
3. Confirm each connection's status chip is green before you plan a launch for that brand.
Organize work by campaign
StretchSocial groups content by the Campaign field, and the dashboard, Insights, and Analytics all chart by campaign. Use a consistent naming scheme so each brand's work is easy to filter mentally:
BrandA — Fall LaunchBrandB — Always-On
Every post you compose should carry a campaign; it's one of the four approval checks and it's what makes analytics meaningful.
Build a client sign-off loop
The Approvals tab is where client governance lives:
- Writers create drafts in Compose, tag them with the brand's campaign, and target that brand's networks.
- The account manager opens Approvals, clicks Review to claim each post, and checks the caption and asset notes against the brand guidelines.
- Approved posts are cleared for scheduling; off-brand posts are Rejected (with confirmation) and sent back to the writer.
- Because rejected posts are blocked, nothing off-brand can slip into the calendar.
If a client requires formal sign-off, treat approval in StretchSocial as the record of that decision — it's visible and auditable.
Schedule and monitor per brand
- Use the Calendar to slot each brand's approved posts, spreading them with the seven-day chart so no single brand or day is overloaded.
- Use Analytics filtered mentally by campaign to report per-brand production and delivery (posts, targets, completed vs. failed).
- Use Insights readiness as a team quality bar across all brands.
Concrete example
You run two clients from one workspace:
- Connections:
Acme LinkedIn,Acme Instagram,Globex X,Globex Facebook— all green. - A writer drafts three Acme posts tagged
Acme — Fall Launchtargeting Acme's LinkedIn and Instagram. - The account manager reviews and approves two, rejects one for a pricing error.
- The two approved posts are scheduled for next Tuesday and Thursday.
- On launch week, Analytics shows Acme's completed jobs climbing, and one failed Instagram job — you fix Acme's Instagram connection and reschedule.
Tips
- Brand-prefix every connection label and every campaign name — it's the single biggest clarity win in multi-client work.
- Keep the Approvals → Waiting count low per brand; a backlog on one client delays their whole calendar.
- Never target the wrong brand's network — double-check the connection label before scheduling.
- Consider a naming convention that sorts brands together alphabetically in lists.
FAQ
Can other organizations see my clients' posts? No. Everything is organization-scoped; you only ever see and write your own workspace's data.
Can I manage two Pages on the same network? Yes — add a separate connection for each, with distinct labels.
How do I prove a client approved a post? The Approvals tab records the approval status on the post; use it as your sign-off trail.
Was this helpful?
Help us improve this article
Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.

