Magnolia’s workflow engine is built upon the jBPM Business Process Management Suite.

The Workflow module provides a four-eye content approval workflow preconfigured in the Pages app. The term "four eye" comes from the fact that an editor creates the content before a publisher approves it. In a standard workflow, the publisher can approve or reject content after review. In case of rejection, the workflow will enter a revision cycle where the editor is informed about reasons for rejection.

The four-eye workflow can best be understood using a diagram.

Four-eye diagram

Workflow is only enabled in the Pages app. However, you can enable it for the Assets app or any other content app.

You can disable workflow for the whole installation of Magnolia if you do not need it. Disabling the workflow may be appropriate for a simple site workforce where there are no separate editor and publisher roles. When the approval workflow is disabled, content will be published to public instances immediately when publication is launched. Removing the Workflow module disables all workflows, not only the content approval workflow. Don’t remove the module if you have custom workflows used for some other purpose.

Custom workflow processes

You can create custom workflow processes to suit your requirements. We recommend you use the Eclipse BPMN2 Modeler plugin available in the Eclipse marketplace.

You can implement a simple 4-eye publishing workflow with tasks. You don’t need the Workflow module or jBPM unless your workflow is more complex, involving three participants or rejection.


DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules