reference · reference
Review reasons
Current review reasons facts for Slash Social.
Review reasons give your team consistent labels for rejections and change requests. Admins configure org-level reasons in Settings; approvers pick from that list (plus any system reasons) when sending work back so creators know what to fix.
What it includes
Review reason governance lives in the Settings work center. The feature is in beta and available on the Team and Scale plans (not on Free or Starter).
| Area | What you can do |
|---|---|
| Custom labels | Add, edit, reorder, or remove org-level review reasons |
| System reasons | Slash Social may attach computed reasons when a post has blockers such as missing media or failed rendering |
| Review flow | Approvers pick one or more reasons on reject or change-request actions; creators see them in the review modal and approval threads |
Slash Social merges custom reasons with system reasons at review time. Creators see the combined list when an approver rejects a post or requests changes.
How to use it
Configure reasons (admin):
- Type
/socialand open Settings. - Open Review reasons.
- Add, edit, reorder, or remove labels, then save.
Use reasons during review (approver):
- From an approval action, choose Reject or Request changes.
- Select one or more reasons from the picker your team configured.
- Submit the action. The creator sees the selected reasons in feedback.
To verify setup, save a new reason in Settings, reject a test post, and confirm the label appears in the picker and in the feedback the creator receives.
Details
- Work center: Settings
- Personas: Admin, creator, and approver
- Plan gate: Team and Scale plans (not Free or Starter)
- Lifecycle: Beta, launch-ready
Reason lists apply at the org level. System reasons appear automatically when item state triggers them; you do not manage those labels in Settings.