Client approval
How clients review a preview and approve the exact version that will go live.
Markdown for agentsEvery release requires a human review of the exact version before it can be published. Client work goes to the designated client approver.
Requesting approval
When a preview is ready, choose Request approval in the console or ask your assistant to send it. The client’s designated approver receives an email with a protected review link.
What the client sees
- They open the link. It works for 72 hours.
- They enter a one-time code that Shortcake emails to them.
- They review the preview and either approve it or request changes.
Clients don’t need a Shortcake account, and the review link can’t be used to sign in to anything else.
The rules that keep approvals honest
- Approval covers one exact version. If anything changes after approval, the release goes back for review.
- No self-approval. The person who built, submitted or sent a release can’t approve it on the client’s behalf.
- Links can’t be reused. A decision uses up the link. Expired, revoked or already-used links stop working, and the client can ask you for a new one.
- Approval isn’t publication. Approving marks the version as ready; someone with publishing permission still has to publish it.
Reviewing your own business site
If you own a self-serve workspace and are editing your own business site, you can explicitly request owner review. You must be an eligible workspace owner and a designated approval recipient. You receive the same emailed link and verification-code flow; the decision is recorded as yours, not as a client’s approval.
This exception does not let an agency or operator approve on a client’s behalf. Your assistant cannot approve for either a client or an owner.
Preview access is separate
The review link protects the approval decision. The hosted preview URL may still be publicly accessible unless hosting access controls are enabled. Check preview access before adding confidential content or sharing the URL.