Skip to main content
A workflow touches content in ways that are easy to miss until you hit them. This page covers the cases worth knowing in advance.

​
Availability

This feature is available on the Custom Enterprise plan only. To enable it for your workspace, contact support@thepublive.com.
Clear the Pending Approval tab for a content type before assigning it a workflow. Enabling a workflow hides that tab, and any entry still sitting in it becomes unreachable from the content list. Approve, reject, or publish every entry there first.
Turning a workflow on changes nothing for existing content at that moment. An entry gets its first stage the first time it is opened or edited after the workflow is assigned to its content type.
The edit returns the working copy to the workflow’s first stage. The live version keeps serving, unchanged, until the working copy reaches a publish-ready stage and is published again. The Unpublished Changes indicator continues to show the difference between the two.Without this, the gate could be bypassed by publishing once and then editing freely.
Unpublishing returns the entry to Draft, and its stage returns to the first stage. The entry then goes through the workflow again before it can be republished.
Entries in the deleted stage return to the first stage, and their history is kept. The confirmation tells you how many entries are affected.
The first action to land wins. The second member is told what already happened, for example that the entry was already moved to Ready to Publish. The entry then refreshes to its current state. This applies equally when two members choose different destinations for the same entry at the same time. Neither choice takes precedence.
A stage can become stuck if the only named member leaves or a role has no members. The workflow editor warns you when it detects this. Resolve it by changing the configuration or by using an override. Content never advances on its own: an entry that skipped a review nobody performed would be worse than an entry that is merely stuck.
Deletion follows your existing delete permissions and is not blocked by stage. The confirmation notes the entry’s stage so you know it is mid-process.
A member can hold both roles. Whether they can review their own work depends only on Prevent self-advancement. With it on at the first review stage they cannot, because they are the one who moved the entry there. With it off, they can.
This is valid. Two stages, Writing and Ready to Publish, is the minimum. It gives you a real gate without a long chain.
No statuses change. Drafts stay drafts, live content stays live, and scheduled content stays scheduled. The publish gate stops applying and publishing returns to normal permissions. Stage history stays in every entry’s timeline.

​
Next steps

Configure workflows

Review the settings that control these rules.

Content Workflows overview

Back to the concepts.
Last modified on November 2, 2026