Most teams run approval on the side, in a Trello card, a spreadsheet, or an email thread the wrong person replied to. The comments drift away from the draft, and by publish time nobody is sure which version got the green light. Maeve puts the approval on the post itself. Pick the approvers, set whether one is enough or all must agree, and the post sits as Pending until they decide. Once approved, it moves into the schedule with the decision on record.
3 days free. Cancel anytime.
Every review starts with one decision: who needs to see it. Send the post to the team for internal sign-off, out to the client as a no-login link, or run both in order so the team clears it before the client ever sees it. From the same box you set whether one approval is enough or everyone has to agree, put approvers in a fixed order when the sequence matters, and drop the post into a review batch.
The table view lays out every post and where its review stands, filtered by status, stage, or date. Flip to Resolved and it becomes the audit trail: who approved, what they decided, when, and the outcome, down to the version they signed off on. Editing a post changes its version, so a fresh round picks up the new one while the old decision stays tied to the version it was made on.
Internal sign-off can be the gate that opens client review. The team approves inside the workspace, then the client review batch goes out as a plain link the client opens without an account. Each batch tracks what is approved, what needs changes, and what is still pending, and you can resend the link or cancel the batch from here.
The decision, the policy, the comments, and the version stamp all live on the same draft, so nothing about a sign-off has to be pieced together later.
Approvals is the sign-off surface. The same posts read differently on the other surfaces, and the decision travels with the draft wherever it goes.
For agreeing the plan before reviewers judge individual posts: free, open to everyone, no account needed.
The internal sign-off surface inside a Maeve workspace. The team picks approvers per post, sets a policy, leaves comments, and decides Approve or Reject. The post sits as Pending until the policy is met, then moves on with the decision attached to the draft.
Software that holds a post in a Pending state while the right people sign off. The point is to put the decision, the comments, and the version stamp on the post itself instead of running approval through email and Slack on the side.
Pick the workspace teammates who need to sign off. Choose Any (one approval is enough) or All (everyone has to agree). Send the request from the post. Approvers see Pending in their queue, read the post, and approve or reject. The post moves on once the policy is met.
Workspace members who have approval access. Role gating is server-side, so you can pick from the right list without checking permissions in your head. The list is per-post.
Both work. On Any, one approval is enough and the post moves on. On All, every selected approver has to agree before the policy is met. Set per request.
The post returns to drafting with the rejection on record. A reason is optional. Approval history keeps the rejection so you know what was decided and when, even after the post gets edited and resubmitted.
Up to you. The approver list is whatever you set when you send the request. Most teams don't put the requester on it, but the workflow doesn't stop you.
An edit changes the content hash on the draft. The next round of approval sees the new version. Earlier decisions stay in approval history with their own hash, so you can tell what got approved and what got edited after.
Approvals is for the team signing off inside the workspace. Client Reviews is the no-login surface for the people outside it. Clients open a per-batch link, identify with the email you invited, and decide without a Maeve account. Run either on its own, or run team-then-client where the team approves first and the client review batch goes out after.
Approval History under the workspace. Every resolved approval has the approvers, their decisions, the timestamps, the outcome (approved, rejected, withdrawn, admin overridden), and the content hash for the version they signed off on. One audit trail per workspace.
It is. The approvals area runs on phones with a list view for what's pending and a detail view for reading a post and deciding. The same approve and reject actions are available on both.
Standard and Premium. The internal approvals area is gated to Standard plan and above. Pricing page has the comparison.