Publish a guide

Publishing is the moment a guide stops being editorial work and becomes something an operator relies on in the field. This page covers publishing immediately; to publish at a set time, see Schedule a publish.

1. 1Step 1:

   Open the guide

   Go to All content (opens the admin console) and open the guide you want to publish. The badge in its Publish card shows where it currently sits.

   Screenshot not captured yet

   content-detail-header

   The content header: title, status, and the publish control.

2. 2Step 2:

   Check what operators will actually get

   A guide publishes as itself — its intro and its ordered list of children. Children with their own draft status do not come along for the ride; each item publishes on its own.

   Open Coverage (opens the admin console) if you want to see, guide by guide, which children are still unpublished before you commit.

3. 3Step 3:

   Clear any pre-publish checks

   If your agency has required checks configured, they appear as a list you must satisfy first — a cover image, a summary, at least one tag, and so on. The publish control stays disabled until they pass.

4. 4Step 4:

   Publish

   Select Publish. There is no confirmation step: the guide is saved, goes live, and you return to All content.

   Screenshot not captured yet

   content-publish-dialog

   The Publish card on a guide.

5. 5Step 5:

   Tell operators (optional)

   Publishing by hand sends no push notification by itself. To send one, open the guide again: published items show a Notify operators card — select Send notification. It goes to operators whose notification preferences include this guide, with a deep link that opens it directly. Operators who have never opened notification settings are treated as opted in.

What happens next

• The guide enters the next delta sync for every operator in your agency. Devices that are offline pick it up when they reconnect; nothing is lost in the meantime.
• Media attached to the guide is prefetched to devices where possible, so the guide is readable with no signal.
• The guide starts ageing against your review interval and will surface in Review due (opens the admin console) when it's time to re-validate it.

Undoing it

Unpublish withdraws the guide from operators — it disappears on their next sync. That needs the Unpublish permission, and it's the correct move if operators must stop using it now.

To correct a published guide while operators keep using the current version, edit it in place. If the guide requires sign-off, or you do not hold Publish, your changes are held: operators keep the released version until someone with Publish selects Release to operators, after any approvals the guide needs, so a correction can't slip out unreviewed.