Customize Approval Workflows
Why customize workflows
Section titled βWhy customize workflowsβThe default workflow in CMP moves content from Draft to Review to Published. This works for simple publishing, but most teams have specific review requirements. A financial services company needs legal sign-off. A global brand needs regional approval for localized content. A product marketing team needs engineering review for technical accuracy.
Custom workflows encode these requirements into the system so that content cannot reach publication without passing every required gate.
What you will do
Section titled βWhat you will doβ- Create a new workflow template
- Define stages and transition rules
- Configure reviewers and routing logic
- Add gate conditions and time limits
- Assign the workflow to a content type
Create a workflow template
Section titled βCreate a workflow templateβ- Navigate to Settings > Workflows
- Click Create Workflow
- Enter a name that describes the process (e.g., βBlog Post - Editorial + Legal Reviewβ)
- Add a description explaining when this workflow should be used
- Click Save to create the template and open the workflow editor
The workflow editor displays stages as a visual pipeline. Every new workflow starts with two stages: Draft and Published. You will add stages between them.
Define stages
Section titled βDefine stagesβAdd stages to represent each review or approval step in your process.
- Click Add Stage between Draft and Published
- Name the stage (e.g., βEditorial Review,β βBrand Compliance,β βLegal Approvalβ)
- Set the stage type:
| Stage type | Behavior |
|---|---|
| Review | Assignee provides feedback; can approve, request changes, or reject |
| Approval | Assignee gives a formal sign-off; binary approve/reject |
| Task | Assignee completes a specific action (e.g., upload translated version) |
| Auto | System evaluates conditions and transitions automatically |
- Repeat for each stage your process requires
Ordering matters. Drag stages to reorder them. Content moves through stages left to right.
Configure reviewers and routing
Section titled βConfigure reviewers and routingβEach review or approval stage needs one or more assignees. You can set reviewers in three ways:
Static assignment β Always assign to a specific person or role:
- Open the stage settings
- Under Assignee, select a user or team
- The same person reviews every content item that enters this stage
Dynamic routing β Assign based on content attributes:
- Open the stage settings
- Under Routing Rules, click Add Rule
- Define conditions (e.g., if content type is βProduct Update,β assign to the Product Marketing team; if campaign is βQ3 Launch,β assign to the Campaign Lead)
- Set a fallback assignee for items that match no rule
Authorβs manager β Route to the content authorβs reporting manager:
- Open the stage settings
- Under Assignee, select Authorβs Manager
- This requires the org chart to be configured in CMP user settings
Add gate conditions
Section titled βAdd gate conditionsβGate conditions prevent content from advancing unless specific criteria are met. This catches incomplete work before it reaches reviewers.
- Open a stageβs settings
- Navigate to Gate Conditions
- Add conditions:
| Condition type | Example |
|---|---|
| Required fields | SEO title and meta description must be filled |
| Minimum word count | Body must contain at least 300 words |
| Asset requirements | Featured image must be attached |
| Checklist completion | Author must check off βSources verifiedβ and βLinks testedβ |
- Set the enforcement level:
- Block β Content cannot advance until the condition is met
- Warn β Display a warning but allow advancement
Set time limits and escalation
Section titled βSet time limits and escalationβTime limits ensure content does not stall in review queues.
- Open a stageβs settings
- Navigate to Time Limits
- Set the maximum duration (e.g., 2 business days for editorial review)
- Configure escalation behavior:
- Notify β Send a reminder to the assignee
- Escalate β Reassign to a backup reviewer or the assigneeβs manager
- Auto-approve β Advance content automatically (use with caution)
Assign the workflow to a content type
Section titled βAssign the workflow to a content typeβWorkflows take effect when assigned to content types.
- Navigate to Settings > Content Types
- Open the content type you want to configure (e.g., βBlog Postβ)
- Under Workflow, select your new workflow template
- Click Save
All new content items of this type will follow the assigned workflow. Existing items in progress keep their current workflow unless you explicitly migrate them.
Test the workflow
Section titled βTest the workflowβBefore rolling out to your team, verify the workflow with a test content item:
- Create a new content item of the type you configured
- Move it through each stage, verifying:
- Correct reviewers are assigned at each stage
- Gate conditions block advancement when not met
- Notifications reach the right people
- Time limits trigger escalation as expected
- Complete the workflow through to the Published stage
- Review the audit trail to confirm all stages were recorded
Common issues
Section titled βCommon issuesβ| Issue | Cause | Fix |
|---|---|---|
| Content stuck in a stage | Assignee not set or user account deactivated | Check routing rules; assign a backup reviewer |
| Gate conditions not enforcing | Condition set to βWarnβ instead of βBlockβ | Change enforcement level to Block |
| Wrong reviewer assigned | Routing rule conditions overlap or have wrong priority | Review rule order; more specific rules should come first |
| Notifications not sending | User notification preferences turned off | Check user settings under Profile > Notifications |