Detailed guide. An unofficial adaptation of User Guide 2.6. Source updated April 14, 2025; reviewed November 6, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Previous: 2.5 Planning Your Content Structure · Chapter 2 overview · Next: 2.7 Interface, Configuration and Content Translation
Goal
Plan who creates, reviews, edits and publishes information. Read about the CMS and entities .
Adapted explanation
An editorial workflow coordinates content creation, review, revision and publication. The source distinguishes authors gathering information, editors reviewing or requesting changes, and publication when ready. Minor corrections and substantial changes may use different review processes.
Available mechanisms
| Mechanism | Source explanation |
|---|---|
| Published/unpublished | Publication status and distinct viewing permissions |
| Revisions | Older versions for supported entity types |
| Workflows | States and transitions beyond a binary status |
| Content Moderation | Roles and permissions for transitions; posts and custom blocks |
| Block placement | Separate preparation from making content visible |
Our design and verification example
Draw draft → review → return/publish and assign responsibility for each transition. Plan tests for anonymous access to unpublished content, authors bypassing review and editing already-published items. Defining states is not proof of effective access control.
Update notes: scheduling and notifications
Keep core Workflows/Content Moderation separate from these optional projects:
| Project | Advisory and condition | Fixed releases in the advisory |
|---|---|---|
| Scheduler | 306 ↗ : editing permission plus web-service editing, such as JSON:API/REST | 8.x-1.7, 2.2.3, 2.3.1; 2.1 unsupported |
| Workflow Notifications | 297 ↗ : inadequate protection of notification settings | 3.0.3 |
These are historical fix references, not permanently recommended versions. Check the installed branch and current project guidance. See the weekly article and existing annotation .
Continue learning
Review permissions and blocks . A workflow plan does not itself verify extension permissions or API behavior.
Sources, credits and changes
Source: Drupal User Guide 2.6 ↗ . Contributors and source links listed in its Attributions: Diána Lakatos ↗ · Pronovix · Grant Dunham ↗ · Jennifer Hodgdon ↗ . Refer to the source for writing, editing and adaptation roles, and to the guide-wide credits ↗ .
Copyright remains with the individual contributors; the official copyright page ↗ states © 2015–2025. Changes include reorganized explanations and procedures, our preparation and verification examples, troubleshooting notes, source-interpretation qualifications and release references. Original screenshots and videos are not reproduced. This adapted text is shared under CC BY-SA 2.0 . It is not an official edition or endorsement. This notice does not license unrelated articles or the site design.
Chapter navigation
Previous: 2.5 Planning Your Content Structure · Chapter 2 overview · Next: 2.7 Interface, Configuration and Content Translation
Chapter 1 details · Chapter 3 · All chapters · Search official information