Product details

Review reasons

Review current review reasons behavior, availability, limits, and operating details for Slash Social.

Review reasons give your team consistent labels for rejections and change requests. Admins configure organization-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 and is available on the Team plan (not on Free or Starter).

Area What you can do
Custom labels Add, edit, reorder, or remove organization-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):

  1. Type /social and open Settings.
  2. Open Review reasons.
  3. Add, edit, reorder, or remove labels, then save.

Use reasons during review (approver):

  1. From an approval action, choose Reject or Request changes.
  2. Select one or more reasons from the picker your team configured.
  3. 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 plan (not Free or Starter)
  • Lifecycle: Launch

Reason lists apply at the organization level. System reasons appear automatically when item state triggers them; you do not manage those labels in Settings.

Public help center

Ask Slash Social

Answers come from Slash Social’s public help center.

Ask about setup, Slack workflows, approvals, publishing, billing, or troubleshooting.

Use public questions only. Don’t share workspace content, credentials, or personal data.