Documentation

Current tasks, prerequisites, and product limits

Browse documentation
Core workflow7 minNoindex · follow

Schedule or publish approved content

Choose an eligible destination, save a deliberate slot, or confirm a supported immediate publish action.

Audience
Operators responsible for delivery
Prerequisite
An approved post and a channel whose current delivery prerequisites are satisfied.
Outcome
The post is deliberately scheduled, published, or held with a clear blocker.

Last reviewed 2026-08-02 · Product Information · v2026.08

Schedule one approved post

Calendar places one ready post at a time.

  1. 1Open Calendar and choose an approved post marked ready to schedule.
  2. 2Confirm the intended channel and its connection or delivery class.
  3. 3Choose an open date and time.
  4. 4Review the schedule confirmation and save the slot.
  5. 5Return to Calendar to verify the Scheduled state.

Truth diagram VIS-03

Schedule approved work

Source reviewed
1Approved post
2Eligible channel
3Choose slot
4Confirm schedule
Approved scheduled work can be delivered in the background when due. /calendar
Explanatory diagram; no customer data or runtime state.

Publish through the supported path

Manual and scheduled delivery are distinct actions.

  1. 1For Publish now, review the selected post and provider state in the confirmation.
  2. 2Confirm the action only when the destination is correct.
  3. 3For scheduled work, wait for the approved item to become due.
  4. 4Confirm the bounded delivery state before treating the item as published.

Truth diagram VIS-04

Match work to a channel class

Source reviewed
1Native connection
2App-managed
3Owned distribution
4Preparation-only
Connection and delivery behavior depends on the selected class. /settings#channels
Explanatory diagram; no customer data or runtime state.
FlywheelBrander does not decide what to publish for you. You review and approve content first. When you schedule approved content for a supported channel, FlywheelBrander can deliver it in the background when it is due.

Read readiness and limits

Approved does not always mean ready for delivery.

  • Native connections require the relevant provider connection and approval state.
  • App-managed and owned distribution paths do not imply native provider readback.
  • Preparation-only Podcast work cannot be scheduled or published by FlywheelBrander.
  • When delivery is unconfirmed, use the available manual verification step and do not infer provider visibility.