Nothing your practice publishes goes out without a named person approving it first. This article explains who can approve, how scheduling works, and what happens if a post fails.
| State | What it means |
|---|---|
| Draft | Being written. Editable. |
| Awaiting approval | Sent for checking. Still editable. |
| Approved | Signed off by a practice administrator. Content is now locked. |
| Scheduled | Approved and given a date and time. |
| Published | It has gone out. |
Two other states appear when something goes wrong: Failed (publishing didn't succeed) and Cancelled (you stopped it).
Only practice administrators can approve content. Anyone with access to the hub can write drafts and request approval; the Approve button only appears for administrators.
This isn't just a hidden button. Approval is enforced by the database itself: a write that sets the approver is rejected unless it comes from an administrator for that practice. Even if something tried to approve content another way, it would be refused.
Once approved, the title, copy and channels can't be edited. Otherwise the text an administrator signed off could be changed afterwards and the approval would mean nothing.
To change approved content, cancel it and start a new draft.
Once approved, pick a date and time and select Schedule. It must be in the future.
Publishing runs on a check every five minutes, so a post goes out within a few minutes of its scheduled time rather than to the exact second. Plan around "shortly after 9am", not "9:00:00".
If a lot of content is due at once, up to 25 items are published per check and the rest go out on the following checks.
You can cancel from any state before it publishes — draft, awaiting approval, approved or scheduled. Cancelled items stay on the calendar for the record but never publish.
Once something has published, cancelling in Nexus can't unpublish it. Delete it on the platform itself.
A single post can target several places at once. Each is published separately, so one failing doesn't stop the others — if Facebook succeeds and X fails, the Facebook post stands and only X is marked failed.
Website and Newsletter are treated as your own channels. Nexus records them as published so your calendar is accurate, but it doesn't post to your website or send your newsletter — you take the approved copy and use it. Direct publishing to owned channels may come later.
A failed channel is retried on later checks, up to three attempts, then marked failed for good so a broken destination doesn't retry forever. The reason is recorded against the item.
Common causes:
If a publishing run is interrupted, anything left mid-flight is tidied up automatically within about half an hour rather than being left stuck.
Two rules are built in deliberately, and neither can be configured away: