Approvals

Approvals turns the posts in your current content plan into a simple sign-off queue. Each post moves through clear states: Draft, Pending approval, Changes requested, and Approved. You submit a post for review, and the account owner either approves it or sends it back with a required note describing what to change. Both the agency and the client can leave comments on any post to discuss it without changing its status. It's built for agencies managing content for clients: the agency can prepare and submit posts on the client's behalf, but final approval is always the owner's call. Approval status shows up on the same posts across the Plan and Calendar views, so a sign-off in one place is reflected everywhere.

1. 1

   Open Approvals

   Go to the Posts workspace and switch to the Approvals view (the /dashboard/approvals link forwards to /dashboard/plan?view=approvals) to see your current plan's posts grouped by status: Draft, Pending approval, Changes requested, and Approved.

2. 2

   Submit a post for approval

   On a draft post, click "Submit for approval" to move it to Pending and put it in front of the account owner.

3. 3

   Approve or request changes

   As the account owner, click "Approve" to sign off, or "Request changes" — which opens a note field and requires you to type what to fix before sending.

4. 4

   Revise and resubmit

   When a post is in Changes requested, edit its content over in the Plan or Calendar view, then come back and the agency can click "Resubmit for approval" to send it through review again. (As the owner you'll instead see "Approve anyway" if it's already good enough.)

5. 5

   Comment to discuss

   Open the Comments thread on any post to leave notes back and forth — both client and agency can comment, and commenting never changes the approval status.

6. 6

   Pull back or reopen

   Use "Pull back to draft" to retract a pending or change-requested post, or "Reopen" an approved one if something needs to change before publishing.

• Always include a clear note when requesting changes — it's required, and it shows on the post as "Requested changes" so whoever revises it knows exactly what to fix.
• Use comments for back-and-forth discussion and reserve the approve / request-changes buttons for the actual decision, so the status stays meaningful.
• Approved just means signed off and ready to publish — Zendora doesn't auto-post, so the actual publishing still happens on the platform itself.
• Approval status carries over to the Plan and Calendar views, so you can see at a glance which posts are cleared to go.