# Publishing

> Put the client-approved version live, and what to expect while it deploys.

Once the client approves a release, a teammate with publishing permission can choose **Publish**. Publishing permission is granted separately; being able to edit a site doesn't automatically let you publish it.

## What gets published

Shortcake publishes the exact version the client approved, pinned to that revision of the code. It respects the repository's protected branch and pipeline, so your normal checks still run.

## Following the deploy

The release shows each stage separately: publication authorized, waiting for deployment, and confirmed live. A release only counts as live once the deployment is confirmed. If the deploy fails, the release stays unconfirmed and you can retry; a retry publishes the same approved version.

## Keeping a record

Shortcake records who requested, approved and published each release, which version it was, and how it turned out, including failed or refused attempts. Review links and codes are never stored in those records.
