Network Posting
Sending a post out to your tribes
Publishing one post from every tribe's own pages: choosing which tribes, and what each of them receives.
Last updated September 2, 2026
Write the post once at organisation level and send it to your tribes. Each one publishes it from their own pages, to their own local followers — which is what a brand campaign should look like.
Choosing who gets it
| Option | Sends to |
|---|---|
| Automatically post to all tribes | Every tribe. For brand-wide announcements. |
| Individual tribes | The ones you pick. For a region, a trial, or a handful of tribes. |
| Tribe categories | Every tribe of a particular type — the right tool when "who gets this" is a property of the tribe rather than a list you maintain by hand. |
What each tribe gets
Their own copy of the post, against their own channels, marked as an organisation post so it is obvious where it came from. Each can carry its own tribe post URL, so local traffic goes to the local page.
The message to tribes
Write one. It is the only context a tribe gets — what the post is for, when you would like it out, and whether they may change it. Two sentences turn a mystery post into something people act on.
CHECK THE CHANNELS BEFORE A NETWORK PUSH
Sending to forty tribes means forty sets of connections have to work. Look at the connection status report first — a tribe with a lapsed Facebook link fails silently and nobody notices until someone asks why the campaign was invisible locally.