Reviewing and Approving Posts
How account-owner approval works -- who reviews a post made on your account, what the queue shows, and what happens at each status.
Reepl's approval model is per account, not per workspace. A post written, scheduled, or edited for a teammate's LinkedIn, X, or Reddit account always waits for that teammate. Only the account owner can approve, reject, or publish it -- not an admin, not whoever wrote it.
The same queue covers LinkedIn, X, and Reddit, and it collects posts however they arrived -- written by a teammate, drafted by Andy, or submitted through Zapier, Make, or the API.
There is nothing to turn on. This applies in every workspace, whatever the workspace settings. See Content Approval settings for what each role can do.
Who can post for a teammate
Only owners and admins can create or schedule a post on someone else's account. When they do, it always waits for that account's owner to approve it -- whatever the workspace setting -- and the composer shows Submit for Approval instead of Post Now. Submitting shows a Sent for approval confirmation.
Finding the queue
Open Create → Content and switch to the Approval tab, or go straight to app.reepl.io/content-creator?tab=approval. Reepl also remembers which tab you were last on, so you land back here next time.
Each card shows the post, who wrote it, which platform it is bound for, when it is scheduled, and a badge if AI generated it. Posts are grouped into up to three sections: Submitted (what you sent in), Needs Your Attention (what you can act on), and Other Activity (posts between two other teammates you can only view).
A post you cannot act on shows a Waiting for tooltip naming the account owner it is waiting for.
Filtering
The toolbar narrows a busy queue by platform and by status (Pending Approval, Changes Requested, Rejected), sorts newest or oldest first, and has a search box for the post text.
What the account owner can do
Approve
Approves the post as it stands. Because a post can sit in the queue past its intended slot, approving opens a confirmation showing the scheduled time. If that time has already passed, Reepl suggests the next free slot instead of silently publishing late. Confirm it or pick another time, then Approve & Schedule.
Request Changes
Sends the post back to its author with a written note. The status becomes Changes Requested and your feedback is attached to the card, attributed to you, so the author can see who asked for what.
Reject
Declines the post outright, with a reason. The status becomes Rejected.
Revert to draft
Takes the post out of the queue entirely and puts it back in Drafts. Available on LinkedIn posts that are still pending or have changes requested. Use this when a post is not wrong so much as not ready, and you would rather it went back to being worked on than sat in review.
Discard
Removes a reviewed post from the queue for good, along with its feedback. There is no undo from inside the app, so a confirmation dialog stands in the way.
Stale posts
A post that has been waiting for approval, or waiting on requested changes, for more than 14 days shows an age badge (for example 14d) with a hint to check that dates, news, and time references are still accurate before approving. The same warning appears again in the Approve confirmation dialog.
What the author does next
A post that comes back as Changes Requested or Rejected stays with its author, who can:
- Edit & Resubmit -- make the requested changes and send it back for review
- Resubmit Without Changes -- put it back in the queue unchanged, which is the right move when the feedback was based on a misreading
- Discard -- remove a rejected or changes-requested post from the queue for good
Editing a post that is already approved
If someone other than the account owner edits a post that is already scheduled (or that failed and is waiting to retry), it goes back to pending approval -- the owner needs to sign off on the new content before it goes out. The owner editing their own post is not affected.
Statuses
| Status | Meaning |
|---|---|
| Pending Approval | Waiting for the account owner |
| Changes Requested | Sent back with feedback, waiting on the author |
| Rejected | Declined, with a reason |
Posts that arrive from elsewhere
The queue is not only for posts people write in the app.
- Andy puts drafts here when its routine is set to Send for review. For Andy's own drafts, the chosen Reviewer and workspace owners and admins can act on them. See Andy's posting routine.
- Zapier, Make, and the API submit into the same queue, so an automation cannot bypass review.
Both raise the approval_requested webhook event, which carries a source field -- so you can route AI-generated submissions differently from human ones. See Webhooks.
Loading older posts
Each status bucket loads its newest 50 posts by default. If a bucket is full, a Load older posts button appears; using it loads up to the newest 100 posts per status.