Docs Documentation
Publishing
Edit freely, then push your changes to the screens when they are ready — now, at a set time, or to one room first. Roll back or hold a stage.
In a workspace that publishes manually, screens never show what you are still working on. They play a release: a snapshot of your stories, scenes, shots, layouts, call sheet, times of day, named conditions, shows and presets, made when someone presses Publish. Until then you can change anything, preview it, and change it again.
Manual or automatic
- Manual — the default for new workspaces, and what we recommend. Edits wait for Publish.
- Automatic — every save goes to the screens at once. Workspaces made before publishing existed start here, so nothing changed for them.
Switch in Settings → Releases. Switching to Manual starts from release 1, which is exactly what plays now, so no screen changes. Switching back to Automatic sends every unpublished edit to the screens.
Publish
Publish sits in the app bar. When nothing waits, it reads just Publish; otherwise it counts the changes.
See what changed
The Publish button in the header says how many changes are not published — 3 changes not published. It opens a list of them by kind, with a small before-and-after sketch for shots and layouts, and the stages they reach.
Add a note
Say what this release is for — Friday dinner menu. The note is kept in the history.
Choose when
Publish now, or Publish at a time in the venue’s time zone. A scheduled release is sent to the screens ahead, so they switch exactly on the minute, even if their network drops before then.
Choose where
Leave it for every stage, or tick Only these stages to roll a change out to one room first. The other stages keep their release until the next publish reaches them.
The Publish dialog: a note for the history, Publish now or Publish at in the venue’s time zone, and Only these stages.
Watch it arrive
After you publish, the dialog follows every screen: Offline, Downloading 12 of 18 files, Ready, Playing. It ends with All 14 screens on release 42, or names the screens still on their way.
Screens download a release in the background while they keep playing the old one, and switch at the end of a shot. The panels of a wall switch together. Nobody in the room ever sees a half-published state.
What never waits for a publish
- Live operations — takes, GO and Back, Blackout, the stage’s TV channel, presenters going live, casts, and rules deciding.
- Data — records and feeds reach the screens on their own. A collection can opt in to waiting: Data → the collection → Fields → Publishing → Changes need publishing.
- Stage settings — shape, rotation, rules, idle, sync and device settings are configuration: they apply when saved.
History and rollback
Settings → Releases lists every release with who made it, when, how (the app, the API or an agent) and the note. Compare shows what one release changed against another. On the screens shows where a release stands on each screen right now.
Roll back to this release makes a new release with the old content, so the history is never rewritten and you can roll forward again the same way. Your working copies stay as they are — they then show as not published.
A scheduled release shows as scheduled until its time. Cancel it before then if plans change; a later Publish now also replaces it.
Settings → Releases: manual or automatic, then the history with Compare, On the screens and Roll back to this release.
Hold a stage
Hold on release 41 keeps one stage on its release — for an event room that must not change mid-event. It ignores newer releases until you press Release from hold; then it moves to the newest one in the background. The rollout view counts a held stage as held, not as late.