Understand content statuses
What each content status means — Draft, In Review, Needs Changes, Approved, Scheduled, Publishing, Published, Failed, Archived, and Trashed — and how content moves between them.
Every content item has a status that shows where it is in the workflow — from a first draft to published, and a few states in between. This page is a reference to each status and how content moves between them.
The main workflow
The status reflects the action you choose. Review is optional on every plan:
- Draft — being written. Drafts are private to your team and not committed anywhere.
- In Review — submitted for review. Reviewers can comment, approve, or request changes.
- Needs Changes — a reviewer asked for changes. The author revises and resubmits.
- Approved — reviewed and cleared to publish. Approved content can be scheduled or published now.
- Scheduled — a saved version queued to publish at a future date and time.
- Publishing — Acrosite is committing the content and, if the project uses a deploy hook, triggering the deployment.
- Published — committed to your repository. If the project uses a deploy hook, the deployment was also triggered.
- Failed — a publish attempt did not complete. The item can be retried.
Other statuses
Two more statuses sit outside the main flow:
- Archived — set aside and out of the active workflow, but kept for reference.
- Trashed — moved to trash, pending permanent removal.
How content moves
- Authors and Editors write a Draft and Request Review → In Review.
- Reviewers Approve → Approved, or Request Changes → Needs Changes (then back to In Review when resubmitted).
- An authorized publisher can schedule or publish a saved Draft, Needs Changes or Approved item. Pending In Review content requires an explicit supersession decision before publishing → Publishing → Published.
- If a publish does not complete, the item becomes Failed and can be retried.
Note
A status like Published means Acrosite committed the content and triggered your deployment. It does not by itself confirm your hosting provider finished the build. Owners and Admins see the build status reported to GitHub in the item's Published File panel — see Build status.
Where you see statuses
Statuses appear on content lists, in the editor, on the Content Calendar, and in the project's Publishing queue. They also help you filter — for example, to find everything that is Approved or Scheduled.
Next steps
- Schedule content to queue a saved version for later.
- Understand Publish Logs to see what happened during a publish.
- Troubleshoot publishing failures if an item reaches Failed.