Availability
This feature is available on the Custom Enterprise plan only. To enable it for your workspace, contact support@thepublive.com. Content Workflows is turned on per workspace. Until it’s on, you see no new columns, filters, panels, or settings, and publishing works exactly as it does today.Workflow configuration and review actions are designed for the desktop dashboard.
Why use workflows
A workflow models the review process your team already follows, for example writer, then editor, then compliance, then publish. The gate it creates is enforced, not advisory. Content cannot be published or scheduled from the dashboard until it reaches a stage you have marked publish-ready. Holding publish permission is no longer enough on its own. The member who approves content does not have to be the member who publishes it. Every stage change is attributed to a member and kept in the entry’s timeline and in your Audit Logs.Core concepts
A transition can carry an optional note. It’s the place to tell the next reviewer, or the author if the entry is heading back to them, what they should know. A workflow has no fixed forward or backward path: a stage’s Next stages can point to any other stage. Every move uses the same note, optional every time.
Stage and status are separate
Every entry already has a status: Draft, Scheduled, or Published. Status answers where an entry is in its publishing lifecycle. A workflow adds a second, independent dimension: stage. Stage answers where an entry is in your editorial process. An entry always has both. The two meet in one place:An entry can become Scheduled or Published only while its stage is publish-ready.Everything else about status is unchanged. Unpublishing, scheduling, and the live version being served separately from your working copy all work as before. For content types that use a workflow, the Approval Pending status is not used. An entry in review is a Draft in a review stage.
When the gate blocks publishing, the Publish control stays visible but disabled. It tells the author which stage the entry must reach and which stage it is in now. It is never silently hidden.
Who can do what
Workflow rules narrow the permissions your roles already grant. They never widen them. Being named in a stage lets you move the entry from that stage and nothing more. It does not give you access to edit or publish.
A stage also never changes who can see an entry. Visibility is decided only by your existing Content Access Policies.
How it fits with Send for Approval
Workflows is opt-in at two levels:- Per workspace. Content Workflows must be enabled.
- Per content type. A content type is governed only once a workflow is assigned to it.
Next steps
Configure workflows
Build stages, set who can act, and assign a workflow to a content type.
Review and move content
Move entries between stages, override a stage, and read the timeline.