Create and publish a post

Before you start

A post brings together the content you want to publish and the channels that should receive it. Start with a clear audience, the destination you intend to use, and a small piece of content that your team can review. Access to a channel, permission to edit a post, and permission to publish are separate requirements.

Choose the correct workspace and confirm that each destination is an active Publishing channel. A provider name in the catalog does not establish that its connection is authorized or that its runtime is available. Resolve connection problems using External Connections before scheduling an important announcement.

Create the draft

1. Open Publishing and start a post from the Dashboard or Create Post flow.
2. Give the post a recognizable name and choose the intended channels. The initial dialog starts the draft; it does not mean the message has been scheduled.
3. Open the composer and write the default content. Add supported assets and review their order.
4. Save the draft while you are still developing it. Complete the required content, channel and schedule fields before moving it into publication.

Use a descriptive name that helps colleagues identify the campaign or announcement. Keep operational notes out of the public message. Where the Posts Agent is available, inspect its proposed text before applying it; an AI response is still content that needs checking.

Check each channel version

The default text supplies the common message. A custom channel variant lets you adapt the wording or supported options for one destination. For example, the email version may need a subject and more explanation, while an SMS version needs a much shorter message. Review the selected channel before editing so that the change lands in the intended version.

Resetting a custom version to Default removes that customization after confirmation. Check attachments, links, formatting and any provider-specific options separately. Facebook and Instagram publishing have structured options whose suitability depends on the target and media. The availability of an editor control does not make every format valid for every provider.

Move from draft to a planned publication

Choose the applicable approval flow, including any default supplied by the queue. Submit the post for review where approval is required. Use the review guide when a colleague requests changes or when you enable automatic correction.

Choose either a one-time publication or a concrete queue occurrence. Check the date, time, destination list and current capacity before confirming. A recurring queue slot is a timing rule; your post must still be assigned to an occurrence. Saving a draft does not reserve every future occurrence, and approval does not bypass inactive channels or invalid content. The scheduling guide explains recurring generation separately.

Follow the result

Use the Dashboard for active authoring and review, the Planner for planned work, and the Archive for historical outcomes. Open post details to inspect the current state, review history and publication receipts rather than relying on a summary count alone.

Different destinations can finish at different times. A provider may report Processing before it supplies a final result, and one channel can succeed while another needs attention. Check the receipt for each target before creating a replacement post. An uncertain provider response is not proof that nothing was published. For mailing lists, acceptance also differs from delivery to every recipient. Continue with publishing troubleshooting when the outcome is incomplete.