The value of writing an article at head office is that it can appear on every tribe's website. There are two ways round that, and which you use depends on how much you want your tribes to have to do.

Pushing it out

From the article, Copy creates copies on the tribes you choose. Each tribe gets its own copy, which it can then edit — a local phone number, a local example — without affecting yours or anybody else's.

Set status for copied articles decides what the copies arrive as. Sending them out as Draft means each tribe reviews before publishing, which is right for anything that needs localising. Sending them Published means the article is live everywhere immediately, which is right for a network announcement and wrong for most other things.

Letting tribes take it

Allow tribes to copy puts the article in front of the tribes and lets them take a copy when they want it, using Copy from Organisation on their own blog screen. Nothing appears on a tribe's site until that tribe chooses it.

This is the better arrangement for a library of evergreen articles. Pushing thirty articles at every tribe fills their blog with material they did not choose; offering thirty and letting them take the six that suit their market produces a blog somebody stands behind.

Child organisations

A network with organisations beneath it — a brand with a separate organisation per country — can use Copy to Child Organisations, either to chosen ones or to all of them. The copies belong to the receiving organisation, which can edit and translate them.

If a mistake does get out, the practical fix is to tell the tribes what to change. On a small network it is quicker to open each copy yourself.