reference · reference
Multi-step approvals
Current multi-step approvals facts for Slash Social.
Multi-step approvals route drafts through ordered reviewer steps. Each step records decisions before content can schedule or publish. Single-step review still works on lower plans; ordered chains require Team or Scale.
What it includes
Multi-step approvals are included on Team and Scale only. They are not on Free or Starter. See Plan comparison and Usage limits for entitlements and caps.
The feature is in beta and may change. Admins, creators, and approvers interact with it from the Plan work center context, approval threads, and workflow management surfaces.
What the capability covers:
- Named approval workflows with ordered steps and assigned approvers per step
- Workflow lifecycle: create, edit, activate, deactivate, set default, and delete
- Step management: add, edit, reorder, remove, and skip steps where supported
- Advancement: when a step completes, the item moves to the next required reviewer until the chain finishes
- Completion: when all required steps approve, the item can transition to approved and continue toward scheduling
- Review from approval threads,
/social-approve, approval notifications, and Workflow cards
How to use it
- Open Workflow, choose Manage workflows, or open Settings, Automation, Workflow Rules to create or edit a chain.
- Add ordered steps and assign approvers for each step. Activate the workflow and set it as default if new drafts should enter that chain automatically.
- Submit or route a draft into the workflow. Approvers act from the approval thread or
/social-approve. - If a reviewer requests changes, address feedback and resubmit. The workflow advances only after each required step approves.
- When the final step approves, the item leaves the multi-step chain and can follow your normal schedule or publish path.
Screenshots on this page show review and scheduling from an approval thread.
Details
| Topic | Detail |
|---|---|
| Work center | Plan (workflow and approval surfaces) |
| Plan access | Team, Scale |
| Lifecycle | Beta |
| Personas | Admin, creator, approver |
| Default assignment | A default workflow can route new drafts into the right chain |
Structured change requests and rejection reasons depend on whether your plan includes review reasons. See Approvals and review governance for how review fits the content lifecycle.