Emergency stop
Bad news breaks, a campaign dies, a typo ships. Pause-all stops new publish claims across the Organization instantly, keeps every draft and future slot intact, and records who did it.
Pausing halts claims for new publishes immediately. An attempt already in flight reconciles safely rather than being abandoned mid-air. Drafts, occurrences, and history remain untouched, so resuming picks up the rhythm where it paused, minus the missed-window catch-up you would hate.
The control sits prominently in the dashboard, requires one deliberate confirmation, and never buries itself in nested settings. Speed matters most exactly when things are on fire.
Straight answers
No. Future occurrences remain; on resume, normal cadence and skip rules decide what is still worth publishing, transparently.
Owner, Admin, and Publisher roles; the pause event and its author are recorded in the audit log either way.
Anyone you grant Admin can, which is usually comforting to them and safe by design because pausing destroys nothing.
Keep reading
Set the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
QueueTempoSet the tempo. Keep showing up.
Set the next beat
Start free, describe your brand once, and watch the next ten post times appear before anything goes live.