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

# Sharing a post for approval

> Send a client a preview link and collect their comments

**Where:** the Calendar, hover a post, **Preview**

Every post has a public preview page. Sending that link is how you get sign-off
without giving anyone access to Postiz.

## What the recipient sees

* The post rendered as it will appear, including media and all thread parts.
* The date it is scheduled for.
* A comment box.

They do not see your calendar, your other clients, your channels, or anything
else in your organisation. No account is required.

## Collecting feedback

Comments left on the preview page come back to you, so a review cycle looks
like:

<Steps>
  <Step title="Draft the week">
    Write the posts and **Save as Draft** so nothing can publish while it is
    under review.
  </Step>

  <Step title="Send the previews">
    **Preview** on each post, copy the link, send them to the client.
  </Step>

  <Step title="Read the comments">
    Feedback arrives against the post it belongs to, rather than in a thread
    of email where nobody can tell which post is which.
  </Step>

  <Step title="Edit and schedule">
    Apply the changes, then switch the drafts to scheduled.
  </Step>
</Steps>

## A practical pattern for agencies

Combine this with [client groups](/general/channels/customers):

1. Group the client's channels under a customer.
2. Filter the calendar to that customer.
3. Draft their week.
4. Send preview links for the posts that need sign-off.
5. Schedule once approved.

## Limits worth knowing

* A preview link is not password protected. Anyone with the URL can read the
  post and comment, so treat it as unlisted rather than private.
* Approval is a conversation, not a state: there is no "approved" flag that
  blocks publishing. You move the post from draft to scheduled yourself.