Content workflow and statuses | Civio CMS Knowledge Base       [ ![Civio Knowledge Base](/storage/branding/01KP4QF0THM695BDF2MG6TX3CY.svg) ](https://nginx.deploy-lagoon-production.districtcms-docs.dh1.amazee.io)  [Articles](/articles) [Releases](/releases)

   [Home](/)   [Knowledge base](/articles)   [Content workflow](/articles?category=9)

Content workflow and statuses
=============================

Updated 2 weeks ago

    Search  Go

   Overview
--------

Content workflow governs how content transitions between different statuses, from initial creation through to publication and eventually archiving. Depending on their assigned role, a user may have permission to move content from one status to another.

![](/storage/M3E18EfDpKWzcoiwBpKPqkMGKsPU73fg6bofYQGV.png)

Default content statuses
------------------------

District includes a default Editorial workflow that manages content through the following statuses:

StatusDescription**Draft**Content is a work-in-progress and has not been finalised. Used while the author is still creating or editing content before it is ready for review or publishing.**Published**Content has been approved and is publicly accessible on the website. Users can view and interact with it according to the site's configuration and access permissions.**Archived**Content that is no longer relevant or outdated. Archived content remains in the system but is not prominently displayed.> **💡 Note:** Some sites may have additional statuses beyond these defaults (e.g. "For Review", "Needs Review", "Rejected"). Check with your site administrator for the full list of statuses available on your site.

Content status transitions
--------------------------

Content moves between statuses through transitions. The default transitions are:

- **Create New Draft** — Creates content in Draft status.
- **Publish** — Moves content from Draft to Published.

Additional transitions may be configured depending on your site's workflow requirements. See **Configure content workflows** for details.

Workflow notifications
----------------------

When content moves from one status to another, the system can be configured to notify users with the appropriate role via email. For example, when content is submitted for review, approvers can receive an email notification automatically.

See **Content moderation notifications** for details on configuring these notifications.

Scheduling transitions
----------------------

Content can be scheduled to automatically transition from one status to another at a specific date and time. This is commonly used to schedule content for future publication or unpublication.

See **Scheduled content transitions** for details.

---

Related articles
----------------

- **Configure content workflows** — How to edit or create workflows
- **Content moderation notifications** — Setting up email notifications for status changes
- **Scheduled content transitions** — Scheduling automatic status changes
- **Compare and restore content revisions** — Working with revision history
- **User roles and permissions overview** — How roles determine workflow permissions

 [    Back to articles ](/articles)

  Table of contents
-----------------

    © 2026 [District CMS](https://www.district.au)