Skip to content

Version Approval

Choose whether new captures go live in your embeds right away or wait for someone to approve them.

Updates: Automatic or Needs approval

Every screenshot has an Updates setting on its page. It decides what happens to your embeds when a new capture comes in.

SettingWhat your embeds show
Automatic (default)The newest capture, as soon as it is ready.
Needs approvalThe live version you approved. New captures wait for someone to approve them before your embeds change.

Set a default for a whole project under Project settings → Updates. Screenshots follow their project unless you change the setting on the screenshot itself, and views follow the page they belong to.

Reviewing a waiting version

When a capture is waiting, the screenshot page shows a banner: New version waiting, with Compare, Approve and Dismiss. Compare opens a slider between the live version and the waiting one. Approve makes the waiting version live. Dismiss stops asking about it, and your embeds keep showing the live version.

The version timeline marks each version as Live, Waiting or older. To go back to an older version, select it in the timeline and choose the Make live link under the timeline (it names the version, as in “Make v2 live”). Public screenshots also show Make live in the Embed section. Making an older version live on an Automatic screenshot switches it to Needs approval, so the next capture does not replace your choice.

The review queue

Waiting for approval in the sidebar lists every waiting version across your team, with a count. Select several and approve them in one go.

Who can approve

Owners, admins and editors can approve, revert and dismiss versions and change the Updates setting. Viewers see what is waiting but can’t change what is live.

Notifications

People who can approve get one email (and a bell notification) when versions start waiting, with a Review link to the queue. A burst of captures arrives as a single email, and a team gets at most one an hour. Unsubscribing from product emails stops the email; the bell notification still appears.

Versions held for review

Sometimes a capture should not go live even on an Automatic screenshot, for example when an AI annotation blur could not be placed with confidence on the new capture. ScreenshotAgent holds that version for review and the banner says why. Embeds keep showing the last version that is safe to show until someone approves the held one.

From the API and MCP

List waiting versions, compare one with the live version, and approve, revert or dismiss from your scripts or coding agent. See Approvals Endpoints and the list_waiting_versions, get_version_diff and approve_version tools on the MCP server.

When to use which

  • Automatic suits documentation that should always match the current UI.
  • Needs approval suits marketing pages and anything customers see, where someone should look at each new screenshot before it goes live.