Autopilot
Autopilot generates and schedules posts for an event from its published page. Nothing sends unless every switch allows it.
Open Social Media → Autopilot for the workspace-wide view, or an event → Social → Settings for that one event.
Only events with a public page appear here — an event with no published website has nothing to write from.
The switches, outermost first
Each one can independently stop a send, and they are read in this order.
1. Platform master switch
Set by Novex, not by you. When it reads Sends disabled, nothing goes out for anyone, whatever your own settings say. Queued posts are still generated and shown in your daily digest, so you can see exactly what would have gone out.
2. Workspace kill switch — all events
Stops every queued and future post for your whole workspace, immediately. There is nothing to cancel afterwards: posts already in the queue are refused as they come due. You can record an optional reason.
While it is engaged, the composer also refuses approvals and says so.
3. The event’s own kill switch
The same thing, scoped to one event: Stop this event / Allow this event.
4. The event’s settings
- Generate and schedule posts for this event — the on/off for that event.
- Post to — which platforms.
- Post from — which accounts.
- Max posts/day per platform — the ceiling a new post has to fit under.
- Quiet hours — a window nothing is scheduled into.
The preview week
When you first enable autopilot for an event, it starts in preview: posts are generated and shown in your daily digest, but not sent, for the first week. The screen shows the date it ends.
It is there so you can see a week of real output before any of it reaches an audience. If you already know what you want, tick Skip the first-week preview and it posts immediately once enabled.
How posts get scheduled
A nightly planner queues posts for each enabled event, respecting the daily limit and quiet hours. Approving a post in the composer adds one to the same queue.
A sender sweeps the queue every few minutes, so a post goes out at the first sweep after its scheduled time rather than to the second. It re-checks every switch above at that moment — which is why engaging a kill switch stops queued posts without you cancelling anything.
Everything queued — planned or composed — shows up in the campaign calendar.
Related
- Composer — generate and approve posts by hand.
- Campaign calendar — see and adjust what is queued.
- Connected accounts — which handle an event posts from.