Workflow and Moderation in Drupal define how content moves through editorial stages before publication.
Enterprise Drupal platforms — such as government portals, media sites, and healthcare platforms — require structured editorial governance to ensure content accuracy, compliance, and quality.
A well-designed workflow architecture enables:
- controlled publishing
- role-based approvals
- audit tracking
- content lifecycle management
- compliance readiness
Senior Drupal developers must design workflows that balance editor flexibility and governance control.
Drupal Workflow System Overview
Drupal provides workflow capabilities using core modules:
- Workflows
- Content Moderation
These modules allow content to move through moderation states.
Example states:
Draft
In Review
Needs Revision
Published
Archived
Workflow Architecture Diagram
Author
↓
Draft
↓
Reviewer
↓
Approved
↓
Publisher
↓
Published
Each transition can be controlled by user roles and permissions.
Moderation States vs Publishing Status
Important distinction:
- Moderation State = Editorial stage
- Published Status = Visibility flag
Example:
A node may be in:
Moderation State: Draft
Published Status: Unpublished
After approval:
Moderation State: Published
Published Status: Published
Real Project Example (Government Portal)
A compliance-driven portal used the following workflow:
Draft → Legal Review → Content Review → Published
Roles involved:
- Content Author
- Legal Reviewer
- Section Editor
- Publisher
Benefits:
- prevented accidental publishing
- ensured policy accuracy
- enabled audit traceability
Workflow and Node Types
Workflows can be applied per content type.
Example:
Workflow A → News Content
Workflow B → Policy Documents
Workflow C → Marketing Pages
This allows tailored governance strategies.
Revision Integration
Moderation automatically integrates with revisions.
Each transition creates a new revision.
Benefits:
- rollback capability
- approval history
- compliance tracking
Database tables involved:
node_revision
content_moderation_state
Workflow with Views
Views can filter content by moderation state.
Example editorial dashboard:
Filter: Moderation State = Draft
Display: Table
Publisher dashboard:
Filter: Moderation State = Needs Review
This improves editorial productivity.
Workflow and Permissions Architecture
Permissions control transitions.
Example:
Author → Can create Draft
Reviewer → Can move Draft to Review
Publisher → Can Publish
This ensures governance enforcement.
Multilingual Workflow Strategy
Each language translation can have its own moderation state.
Example:
English Version → Published
Spanish Version → Draft
This supports staggered translation publishing.
Workflow in Headless / API Context
APIs can expose moderation states.
Example:
GET /api/events?state=published
Frontend apps show only approved content.
Common Mistakes
- using a single workflow for all content
- giving publish permission to too many roles
- disabling revisions in moderated content
- not building editorial dashboards
- ignoring translation moderation
Workflow and Moderation in Drupal allow content to move through structured editorial stages such as draft, review, and published. Using the Workflows and Content Moderation modules, developers can define moderation states and transitions controlled by user roles. This enables enterprise governance, audit tracking, and controlled publishing while integrating with revisions, Views dashboards, and multilingual content strategies.
Recall
- What is the difference between moderation state and published status?
- How do workflows integrate with revisions?
- Can workflows be applied per content type?
- How can Views be used with moderation states?
- Why is moderation important for compliance-driven platforms?
Memory Trick
Workflow = Editorial Journey
Moderation = Governance Control
Revisions = Audit History
Permissions = Transition Rules