Broadcasts
Push one post to many workspaces at once.
For Hub admins
Workspaces cannot edit broadcasts. They appear read-only on the workspace calendar. If you want workspaces to customize the content, use a Template instead.
How it works
A broadcast lets you write one post and send it to many workspaces at once.
- You create a broadcast in the post editor (Hub only).
- Flamel copies the post into each targeted workspace's queue.
- Each copy publishes to that workspace's own connected accounts.
- Variables resolve per workspace at publish time, so every location gets a personalized version.
Create a broadcast
The broadcast editor mirrors the regular post editor, with three extra options: who receives it, which account types it targets, and when it publishes. Follow the steps below.
Open the broadcast editor

Click New Broadcast in the top nav. This option is only available from a Hub. The editor opens with the same composing tools you use for a normal post, plus the broadcast settings covered in the next steps.
Choose which workspaces receive it

Pick your audience for this broadcast:
- All workspaces for network-wide announcements.
- Specific groups for region-specific or tier-specific campaigns.
- Selected workspaces for one-off, targeted broadcasts.
- Exclude to remove specific workspaces from any of the selections above.
Choose the account types
You pick account types (Instagram, Facebook, LinkedIn), not specific accounts. Each workspace's account of that type receives the broadcast.
Missing platforms are skipped
Workspaces that do not have a connected account for a selected type simply do not receive that version. Only workspaces with that platform connected get the post.
Set the timing
Choose how the broadcast publishes across your workspaces:
- Same Time: everyone posts simultaneously. Best for time-sensitive announcements.
- Staggered: spread the posts across a window. This avoids an "obviously automated" feel across the network.
- Local Time: "9 AM" means 9 AM in each workspace's own timezone.
Add variables to personalize each copy
Use variables in your copy so each workspace's version fills in its own details at publish time:
{{location.name}} {{location.city}} {{location.state}}
{{location.phone}} {{location.address}} {{location.website}}
{{custom.<field_key>}}
For example, this template:
Visit {{location.name}} in {{location.city}} for our summer sale!
Call {{location.phone}} to learn more.
resolves for the Downtown Store in Chicago as:
Visit Downtown Store in Chicago for our summer sale! Call 312-555-0100 to learn more.
See Custom variables for the full list of fields you can use.
Preview before sending
Click Preview, then pick a workspace to see exactly what that location will post. Confirm the variables resolve correctly for a few different workspaces before you schedule or send.
Broadcast statuses
After a broadcast goes out, track its progress with these statuses:
| Status | Meaning |
|---|---|
| Scheduled | Waiting to publish |
| Publishing | Sending to workspaces |
| Published | Done |
| Partial | Some workspaces failed (usually expired connections) |
| Failed | Couldn't complete |
Recovering from a partial failure
Open the broadcast to see which workspaces failed. The most likely cause is an expired connection. Ask those owners to reconnect, then optionally retry just the failed workspaces.
Broadcasts vs Templates
Both push Hub content to workspaces, but they serve different goals. Use this comparison to decide which fits your campaign:
| Broadcast | Template |
|---|---|
| Hub controls content | Workspace customizes |
| Auto-distributed | Workspace chooses to use |
| Same message everywhere | Adapted per location |
| Hub-driven campaigns | Workspace creativity |
Use broadcasts when consistency matters. Use templates when local customization adds value.
Letting workspaces broadcast (sub-workspaces)
For regional managers who run multiple sub-workspaces, you can let them broadcast to their own group. Turn this on under Hub Settings, Permissions, Allow Workspace Broadcasts.