> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postsider.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Approval workflow: review posts before publishing

> Submit posts for review, approve or reject them, and connect approval workflows through the dashboard, REST API, or MCP.

PostSider's approval workflow is optional. An organization can use it for selected posts without forcing every post through review.

## Dashboard workflow

1. Create a post as a draft.
2. Click **Send for approval** in the composer for a new post, or use the post actions menu for an existing draft.
3. An Admin or Owner reviews the post, media, channels, and scheduled time.
4. The reviewer approves the post or rejects it with an optional note.
5. An approved post returns to the publishing queue. A rejected post returns to draft so the author can edit and resubmit it.

Approvers receive notifications when review is requested. The author receives the resolution and rejection note when available. Guest review links can be used for time-limited external review.

<Warning>
  A post in **Pending approval** cannot be dragged into the publishing queue. Approval is a deliberate state transition, not a visual label.
</Warning>

## REST API

Create a draft, then request and read approval through the public API:

```bash theme={null}
curl -X POST https://api.postsider.com/public/v1/posts/post_abc123/request-approval \
  -H 'Authorization: your-api-key'

curl https://api.postsider.com/public/v1/posts/post_abc123/approval \
  -H 'Authorization: your-api-key'
```

The approval response contains the status, reviewer note, request time, and resolution time. If no approval exists, the API returns `{ "status": "NONE" }`.

## MCP

Agents can use `postsider_request_approval` and `postsider_get_approval_status`. Approval is not automatically applied to every post, so an agent should request it explicitly when a human review is required.