Search by

drupal / mutamad_workflow

Drupal-Infrastructure

Editorial approval for Mutamad: an editor drafts, an approver publishes — never the same person — with content locking, email notifications, a required reason for every edit and an audit trail of every decision. Aligned to NCA ECC-2:2024 1-3-1 and 12-2.

Package info

git.drupalcode.org/project/mutamad_workflow.git

Homepage

Issues

Type:drupal-recipe

pkg:composer/drupal/mutamad_workflow

Statistics

Installs: 69

Dependents: 2

Suggesters: 0

1.0.x-dev 2026-11-15 08:37 UTC

This package is not auto-updated.

Last update: 2026-11-16 06:07:01 UTC


README

Mutamad Workflow — سير العمل

Mutamad Workflow

Editorial approval for Mutamad: an editor drafts, an approver publishes — never the same person — with content locking, email notifications, a required reason for every edit and an audit trail of every decision. Aligned to NCA ECC-2:2024 1-3-1 (separation of duties) and 12-2 (event logs).

Built and maintained by iSpectra.

The workflow

Draft ──Submit for review──▶ In review ──Approve and publish──▶ Published ──Archive──▶ Archived
  ▲                              │                                  │                     │
  └──────Return to author────────┘                                  └──Create new draft───┘

Create new draft also saves a draft as a draft, and starts a new draft of a published page — the published version stays online until the new one is approved. New pages start as drafts.

RoleCan
Content editorCreate drafts, submit for review; sees every draft
Content approverAlso approve and publish, return to the author, archive; sees every draft
Site administratorMoves no content

Once submitted, a page waits for the approver. Nobody but the approver takes it out of review — by publishing it or returning it to the author. An author who wants to change a submitted page asks for it back.

Separation of duties

Only the approver publishes — their own pages too, as shipped.

A second approver for an approver's own work is the site's choice, off as shipped. Turned on, an approver does not publish a page whose latest version they wrote: they submit it like anyone else, and another approver — or the administrator — publishes it. The rule holds on the edit form and on the Change to control shown on the page, and the refusal says why; with mutamad_canvas_controls, Canvas pages and their translations follow it too. It is the ECA rule Mutamad: an approver does not publish their own work, turned on or off at Configuration → Workflow → ECA.

A small team with a single approver that turns it on needs a second approver, or the administrator, for that approver's own pages.

A reason for every edit

Saving a change to an existing page asks for the Revision log message: what changed and why. It is kept with that version, beside who made it and when, and shown on the page's Revisions tab. A new page needs none. This applies to every content type, those created later included (ECA rule Mutamad: a reason for every edit).

Content lock

One person edits a page at a time, on every content type. Whoever opens the edit form second is told who holds the lock. The lock is released when the first person saves or leaves the page, and stops counting after 30 minutes without activity. Editors, approvers and the site administrator can break a lock.

Notifications

WhenWho is emailed
A page is submitted for reviewEvery content approver
A page is publishedIts author
A page is returnedIts author, with the approver's reason

Emails go to the site address with the recipients in Bcc, so they do not see each other's addresses. The texts are in English, and are translated with the rest of the site's configuration.

They are delivered only if the server can send mail. On a server without a mail agent that delivers, set MUTAMAD_MAILER_DSN to the entity's mail relay (settings.mutamad.php, in the Mutamad project template); otherwise no approver hears that a page waits, and nothing says so.

Audit trail

Every change of state — who created, submitted, approved, returned or archived what, and when — is recorded in the admin audit trail (admin_audit_trail_workflows), with the rest of Mutamad's administrative events.

Content types

The workflow applies to none until a content type joins it — the Page (mutamad_content_base) is the first. A recipe that creates a content type adds it:

config:
  actions:
    workflows.workflow.mutamad_editorial:
      addNodeTypes:
        - news

Or at Configuration → Workflow → Workflows → Editorial approval. Content Lock, the two ECA rules and the notifications need nothing per type.

Left for later

  • Refusing to publish Secret or Top Secret content, which needs the classification field (mutamad_classification).
  • Reminders before a page's review date, which needs a review-date field on the content types (mutamad_content_gov).

Not included: Scheduler (a scheduled page is published by cron, where these rules do not run), Access Unpublished (it shares drafts through secret links), and a workflow in which the content editor both writes and publishes.

Requirements

Drupal core 11.4, and Mutamad Roles for the job roles; the recipe applies it first. Composer brings Content Lock, Content Moderation Notifications, Admin Audit Trail and ECA.

Apply it to an existing site

composer require drupal/mutamad_workflow
drush recipe ../recipes/mutamad_workflow

Then add the content types to the workflow. Existing pages keep their status when their type joins: published pages are Published, unpublished ones Draft. The recipe cannot take a permission away: check that no role other than the content approver holds the Approve and publish, Return to author or Archive transitions.

Licence

GPL-2.0-or-later.

Maintainers

iSpectra

Built and maintained by iSpectra (on drupal.org).