Stop everything
One button that holds every channel at once, for a mistake, a crisis or anything else that needs a moment's silence, and planned silences that do the same for a period you set ahead.
Stop everything sits under Publication, below Syndication. It is shown to the owner and to whoever holds the Operations or the Approvals permission: the people who run the channels and the people who hold posts back. The button is on every plan; planned silences are part of Enterprise.
What stopping does
While everything is stopped, every channel of the workspace counts as paused, exactly as if you had pressed Pause on each one under Channels, and one thing more:
- New content makes no post. A feed update, a post list's post coming due, an event on a custom feed and a feed update released by a channel's schedule are received and filed, and make no post. A clip that finishes rendering meanwhile makes no post either. Nothing piles up, so resuming does not release a flood of whatever came in while everything was stopped.
- Posts already scheduled wait. They go out when you resume.
- Nothing already handed over leaves. Every email, webhook call, platform connector post and syndication delivery that was still to be sent stays where it is, its attempts unspent, and goes out when you resume. A resend, a retry or an update you ask for meanwhile waits with them.
- A request to delete still goes out. Taking something down is often what a crisis needs most, so a delete request on Posts is sent at once.
Channels you paused one by one before stay paused when everything resumes: the stop never changes a channel's own switch.
Stopping and resuming
Stop everything opens a dialogue that says what happens and asks why, which is optional: whatever you write is shown on the card and in the audit log, so whoever comes next knows what happened. The button is red, because it is not pressed lightly.
While stopped, the card says who stopped it, when and why, and how many posts and deliveries are waiting, and every screen of the dashboard carries a note at the top, Everything is stopped: nothing goes out, which leads here. A stop forgotten is a workspace that posts nothing for days, so it is never only on this screen.
Resume everything lets every channel work again. What waited goes out at once, so cancel first on Posts anything that should no longer go out. Content that arrived while everything was stopped made no post and does not come back.
Both are written to the workspace's audit log, which an Enterprise workspace reads on Compliance.
Planned silences
A planned silence holds every channel for a period you set ahead, exactly as Stop everything does, and starts and ends by itself: the run-up to an election, a listed company's closed period before its results, a national mourning. Part of Enterprise.
The Planned silences card lists them with their start, their end and where they stand (Planned, On now or Over); silences that ended more than a month ago drop off the list, and the audit log keeps every one. Plan a silence asks what it is for, when it starts and when it ends, in UTC like every time in the dashboard. A silence lasts at most 366 days, and a workspace may have 50 still to end.
Settings on a row changes one, an end brought forward included. Remove takes it off the list; removing one that is on ends it at once, and what waited goes out.
While a silence is on, the note at the top of every screen says Planned silence until and its end. If Stop everything is pressed during a silence, both have to be over before anything goes out again.
A workspace that leaves Enterprise keeps its planned silences on the list, where they hold nothing back any more; remove them, or use Stop everything.
Through the API
A key with Channels: read reads whether the workspace is stopped or silent, and one with
Channels: write stops, resumes and plans silences, at /v1/channels/stop and
/v1/channels/silences: see the API reference. The MCP server
has no tool for it: a switch that stops every channel is pressed by a person.