Document approval workflow in Confluence

The problem

Policy says “get approval before publish,” but teams track it in email, comments, or a spreadsheet. Drafts get edited mid-review. Nobody knows who approved what — or when.

How Churrie Workflow helps: a fixed pipeline on every workflow-enabled space — Draft → In Review → Approved → Published, with Rework after rejection. Review progress shows on the page byline.

Pipeline stages

  • Draft — author works privately
  • In Review — ACL lock; only reviewers, approver, and admins can edit
  • Approved — quorum met; awaiting final approver sign-off
  • Published — content copied to publish targets
  • Rework — after reject; creator fixes and resubmits

Reviewer controls

  • Quorum: all reviewers, any one, or majority
  • Reject re-review: reset all, keep prior approvals, or approver only
  • Delegate approver; priority and due dates on workflow items
  • Email and in-app notifications on transitions

Compliance-friendly reports

Open Space Tools → Churrie WorkFlow Reports for Awaiting Completion, Completed Approvals, and optional Audit log (who, when, stage change, notes).

Full reference: Churrie Workflow features · Get started