Edit or reject from threads and inline actions

Goal

Edit copy or reject a post from the approval thread or from inline quick actions without leaving the conversation where the draft was shared. Thread and inline paths use different edit modals and have different effects on approval state, so choose the entry point that matches what you need.

When to use this

Use this workflow when:

• You are an approver or admin on the brand and a post is still in review.
• You spotted a copy fix in the approval thread and want to correct it before approving.
• You need to reject or request changes with structured review reasons.
• You see the post in App Home, My Work, or another view with inline quick actions and want a fast edit or rejection.

Do not use this workflow after the post has already left review. Actions are only available while the post is in an approvable state.

Before you begin

Confirm the following:

• You have approver or admin permissions on the active brand.
• The post is still in review and has not already been approved or rejected.
• You know whether you are editing from the approval thread or from inline quick actions. These paths behave differently after submit.

Steps

Edit from the approval thread

1. Open the approval notification or thread for the post.
2. Choose Edit.
3. Update the caption or copy in the modal.
4. Submit the edit.

After a thread edit, the post returns to pending approval so reviewers can confirm the new copy. The draft thread message updates to reflect your changes.

Edit from inline quick actions

1. From App Home, My Work, or another view that shows the post with quick actions, choose Edit.
2. Update the copy in the modal and submit.

Inline edits update the draft thread message without resetting approval state the same way a thread approval edit does. Use inline edit for quick copy fixes when you do not need to send the post back through the full pending-approval cycle.

Reject or request changes

1. Choose Reject from the approval thread or from inline quick actions.
2. Select a review reason and add detail when the form asks for it.
3. Submit the rejection.

The creator receives structured feedback tied to your review reasons configuration. Rejected posts move to changes requested and leave the approval queue.

Confirm it worked

You know the action succeeded when:

• Rejected posts leave the approval queue and no longer appear in pending approvals.
• Edits from the approval thread show pending approval again until a reviewer approves the updated copy.
• The draft thread message reflects the latest copy after either edit path.
• The creator receives rejection feedback with the review reason you selected.

Troubleshooting

Edit or Reject buttons are missing

Confirm you have approver or admin permissions on the brand and that the post is still in review. Actions are not available after approval or final rejection.

Thread edit did not return the post to pending approval

You may have used inline quick actions instead of the approval thread. Inline edits update copy without the same approval reset. Use the approval thread Edit action when you need the post back in pending approval.

Rejection modal shows no review reasons

An admin needs to configure review reasons for the brand. See Configure workflow rules and routing or ask an admin to open Review reasons in automation settings.

Post stays in review after edits

Some edits require a fresh approval cycle. If the post does not advance, see Recover a post stuck in review.

Draft thread message shows old copy

Wait a moment for the thread message to update. If it still looks stale, refresh the thread or reopen the post from App Home.

Use the post detail view as the source of truth when a thread and modal disagree after an edit.

Related docs

If a post stays in review after edits, see Recover a post stuck in review. For approval policy context, read Approvals and review governance.