Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Approval workflows overview

How approval before publishing works in Exponential - workflows, the Approve event, triggers, the collaboration inbox, pending versions and the workflow cronjob - explained for public bodies that need a documented…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/operations/editorial-workflows/approval-workflows-overview.md

On this page

Approval workflows overview

This page is for web managers, editors-in-chief and administrators who must make sure content is signed off before it reaches the public. In Exponential the sign-off is a workflow with an Approve event, connected to the publishing operation by a trigger. The facts come from Workflows; this page explains the moving parts and the decisions a public body makes.

Contents

  1. The moving parts
  2. What happens to one article
  3. Decisions to make
  4. Prerequisites people forget
  5. What approvals do not cover
  6. Related pages

The moving parts

PartWhat it isWhere
Workflowan ordered list of events, in a workflow groupSetup > Workflows (/workflow/grouplist)
Approve eventa step that holds a version until an approver decidesthe workflow's edit page
Triggerconnects a workflow to an operation, before or after itSetup > Triggers (/trigger/list), row Before publishing content
Collaboration itemthe approval request approvers decideMy account > Collaboration (/collaboration/view/summary)
Pending versionthe version waiting for the decisionMy pending items (/content/pendinglist)
Workflow processone running approval for one versionSetup > Workflow processes (/workflow/processlist)
Workflow cronjobworkflow.php, in the frequent part by default; publishes approved versionsSetup > Cronjobs

What happens to one article

  1. An editor presses Send for publishing. The version becomes pending.
  2. The trigger Before publishing content starts the approval workflow; the Approve event creates a collaboration item for the approvers and the process waits.
  3. An approver opens the request, reads the preview and presses Approve or Deny (with a comment).
  4. At the next run of the workflow cronjob: approved versions are published; denied versions go back to the author as drafts (Workflows, section 1).

The editor follows it on My pending items, which says what holds the version and links to the approval.

Decisions to make

QuestionWhere it is setTypical public-sector answer
Which content needs approval?Approve event: Affected sections, Affected languages, Affected versionsthe public sections, all languages, all versions
Who approves?Groups who approve content (prefer groups to named users)an approvers' group per area
Who may publish without approval?Excluded user groupsa small, documented group; see Emergency publishing bypass
New pages only, or every change?Affected versions: all, new objects, updatesall versions, if a typo fix must also be checked; otherwise new objects only
One approver or two?one Approve event, or two in sequencesee Two-person rule
Separate legal or language review?an extra Approve event, a second group, or an object statesee Legal review step, Multilingual approvals

Setting up the event field by field: Setting up the Approve event.

Prerequisites people forget

  • The workflow cronjob must run. Without it, approved content is never published. The status bar of Setup > Workflow processes says whether workflow.php is scheduled (Workflows, section 3.4).
  • Approvers need the rights to decide: the collaboration module and content/versionread (Role design: approvers).
  • One workflow per trigger. To run several workflows on publishing, use a Multiplexer event in the triggered workflow.
  • Test with sample data: ./console exp:collaborationsampledata --dry-run --allow-root-user shows what it would create; --remove takes it away again (Workflows, section 3.6).

What approvals do not cover

  • Removing, moving and hiding content are other operations; the trigger list shows which operations can start a workflow. Limit those rights by role instead.
  • The approver's own content is let through by the Approve event.
  • Excluded user groups publish directly.
  • An approval checks a version, not later changes: the next version needs its own approval (with Affected versions set to all).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x