← All updates

Engineering / Field note

Drupal’s publishing workflow needs more than an Approved label

Editorial status, permission to publish and the revision visitors see are separate decisions in Drupal. Connecting them makes approvals easier to trust and drafts easier to review.

By Zyel · Published · 4 min read

An Approved label tells people where an article sits in an editorial process. The website also needs to know who may publish it and which revision readers should receive. Drupal’s established core publishing model separates those concerns: Workflows defines states and transitions, while Content Moderation connects transitions with roles and permissions. A useful editorial design makes those decisions agree. [4]

That distinction matters to content owners as much as developers. A reviewer can approve the wording while a publisher chooses the release time. Someone can keep improving a page while its existing version stays available. Those arrangements work best when the team has a shared meaning for approved, current and public. A status badge has a small vocabulary and a surprisingly large job.

A state describes the process; its settings control behaviour

Drupal’s Workflows documentation describes states and the transitions connecting them. Content Moderation states also carry publishing and default-revision settings. The published setting affects the content’s publication status; the default-revision setting affects which revision is loaded through the usual entity-loading paths. A custom state name alone does not explain either setting. [2]

In a hypothetical newsroom, Approved could mean that copy review is finished but release is waiting for a scheduled announcement. In another organisation, approval and publication might happen together. Neither meaning follows automatically from the word. The workflow’s settings need to express the organisation’s chosen policy. [2]

The connecting paths matter too. Drupal lets a workflow define the source and destination states for a transition. If a hypothetical workflow includes a permitted route straight from Draft to Published, the existence of a Review state elsewhere does not make that review mandatory. [2]

Our interpretation is that an approval record should answer a business question: what decision was made, about which revision, and what remains before release? A diagram with reassuring labels is useful only when the available paths preserve that meaning. More boxes are not automatically more control.

Authority comes from the account’s permissions

Drupal’s user guide defines permissions as rights to perform actions, grouped into roles. Signed-in users receive the Authenticated user role and can hold additional roles. Consequently, calling a role Reviewer does not establish a boundary by itself; the account’s granted permissions determine its authority. [3]

Consider a hypothetical team with Authors, Reviewers and Publishers. The intended separation might be drafting, approving copy and releasing it. If an author also holds another role that grants publishing rights, the account can have more authority than its everyday job title suggests. Role combinations deserve attention alongside the individual role definitions. [3]

For Zyel, the practical acceptance question is whether the ordinary accounts doing the work can exercise exactly their intended authority. A successful administrator demonstration leaves that question open. The useful evidence includes an author reaching review, an authorised publisher completing release, and an account without publishing authority receiving a refusal. These are proposed acceptance outcomes, not results claimed for a particular site.

The latest revision can differ from the public one

Content Moderation supports a published version remaining live while a separate working copy moves through review. Its documented example shows an author editing an already published page, saving a draft and viewing that newer copy through Latest version while readers continue to see the published page. This is a deliberate editorial capability. [1]

Imagine a service page whose published revision has the current opening hours, while a newer draft contains next month’s hours. A reviewer opening the public address could reasonably think the changes were lost. A visitor seeing today’s hours is receiving the intended publication. The two people need different views of the same content item. [1]

The module’s documentation also highlights permissions for viewing the latest version and an author’s own unpublished content. Draft-review access therefore deserves its own decision; it does not follow simply from being able to see the public page. [1]

Our operational takeaway is to make review context visible. A review link, revision identifier and clear publication status help people discuss the same copy. Otherwise, perfectly accurate feedback can be attached to the wrong version. The familiar instruction to “check the page” is doing rather too much unpaid work.

Public visibility is a separate promise

The Drupal User Guide distinguishes viewing permissions for published and unpublished content. It also describes revision tracking as retaining older versions that can be revisited or reverted. Together, these capabilities support an editorial history without requiring every retained version to be the version visitors receive. [4]

The documentation behind this model spans established guidance: the Workflows overview was updated in November 2024, the User Guide chapters in April 2025, and the Content Moderation overview in August 2026. The enduring management decision is who may draft, review, release and inspect each version. [1] [2] [3] [4]

A well-defined publishing workflow gives each of those decisions an owner. Staff can tell whether review is finished, publishers can identify the approved revision, and readers receive the intended public version. That is the useful standard for an Approved label: everyone understands the promise, and the website’s permissions and revision behaviour keep it.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. Content Moderation overviewDrupal · Checked Nov 17, 2026
  2. Workflows overviewDrupal · Checked Nov 17, 2026
  3. Users, Roles, and PermissionsDrupal User Guide · Checked Nov 17, 2026
  4. Editorial WorkflowDrupal User Guide · Checked Nov 17, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.