Skip to content

Workflows

Jump to bottom
Phillip Dornauer edited this page Apr 1, 2026 · 1 revision

Workflows

Workflows add a multi-step editorial approval process before content goes live. A typical setup is Written → In Review → Approved → Published.

Creating a Workflow

Go to System → Workflows and click New Workflow.

Workflow Steps

Property Description
Name Step label (e.g. "In Review")
Sort Order Position in the sequence
Reject Enabled Whether a reject button appears at this step
Reject To Step Which step to fall back to on rejection
Allowed Groups Which user groups can advance past this step (empty = anyone)

Connecting a Workflow to a Blueprint

In the blueprint editor, choose a workflow under Workflow. All items of that blueprint will go through the configured steps before being published.

How It Works

  1. A new item starts as draft with no workflow step.
  2. An editor clicks Advance → the item moves to the first step.
  3. Each Advance moves the item one step forward.
  4. At the final step, Advance publishes the item.
  5. Retreat moves the item one step back.
  6. Reject (if enabled) moves the item to the configured reject_to_step.

Reject vs. Retreat

  • Retreat — steps back one position. Used by an editor to undo their own advance.
  • Reject — sends the item to a specific configured step with a rejection comment. Used by a reviewer to send content back to the author.

Example: Blog Editorial Workflow

Written  →  In Review  →  Approved  →  Published
   ↑              |             |
   └──────────────┘ (reject)    └─ (reject → In Review)
  • Written: no reject
  • In Review: reject → Written; allowed groups: Editors
  • Approved: reject → In Review; allowed groups: Senior Editors

Workflow in the Item Editor

When an item has a workflow:

  • The sidebar shows the current step name
  • Advance and Retreat buttons appear
  • If reject is enabled, a Reject button appears with a comment textarea
  • Transition history is recorded in the activity log

Clone this wiki locally