Orkestia
Blog
Media

Posts and review

Write a post for a channel, schedule it, get a yes, and follow it until it is live. Edit, reschedule, cancel and retry

TL;DR

  • New post: pick where (YouTube Short or video, Instagram Reel or feed, LinkedIn), a look, a file, a cover, a title, a caption and a time. Send for review.
  • Review: the reviewer approves or asks for changes with a note. Nothing goes live without a yes.
  • Calendar shows the month, one slot per channel. Today shows what waits and what goes out next.
  • Before it goes out, a post can be edited, rescheduled or cancelled. A post that did not go out says why and can be tried again.

Write a post

Studio → New post:

  1. Where should this go? YouTube Short, YouTube video, Instagram Reel, Instagram feed or LinkedIn.
  2. Which profile? A look that posts to that channel. No look yet? Create one in Profiles.
  3. File: a video or photo from Files. LinkedIn accepts words alone.
  4. Cover: a cover from the look's kit (not for LinkedIn).
  5. Title, caption and time.
  6. Send for review.

Each post is for one channel. To post the same video on two networks, send two posts (publisher.post.create-with-approval).

Review

Waiting → Review lists posts that need a yes. The reviewer approves or asks for changes with a note ("Lead with the role, not the kitchen."). Asked-for-changes posts come back to the writer (publisher.review.decide, publisher.review.list).

The reviewer is set in Review settings: a person or a Staff agent.

Change a post before it goes out

From Today, Calendar or Review:

ChangeWhat happens
New words, file or coverIt goes back to review
Only the timeIt keeps its approval
CancelIt is removed; live posts cannot be cancelled

Workflows: publisher.post.revise, publisher.post.cancel.

When a post does not go out

The post shows why in plain words and links to it when it is live. Try again sends it back to the schedule when it is still approved, or to review when it is not (publisher.post.retry).

Approved posts are published when their time comes by the organization's publishing schedule (publisher.post.publish-due).