Skip to main content

Publish requests

Publish requests add an approval step to the publishing workflow. Instead of changes going live the moment you publish them, a creator submits a request and an approver reviews it. Only approved changes reach live screens. This keeps unreviewed content off your displays — useful for brands, franchises, or any team with content governance requirements.

How the workflow works​

  1. Submit — a creator prepares changes and submits a publish request instead of publishing directly.
  2. Review — approvers see the request in a centralised queue. They can review what's being changed.
  3. Approve / Reject / Cancel — the approver accepts, rejects, or cancels the request.
  4. Go live — approved changes are published to the affected screens.

Submit a publish request​

  1. Make your changes to the screen, layout, or content as normal.
  2. Instead of Publish Changes, choose Submit for Approval.
  3. The request appears in the Publish Requests queue for review.

Manage the queue​

The Publish Requests page lists every pending and recent request across your team, giving approvers a single place to act on submissions. For each request you can:

  • Approve — accept the changes and publish them.
  • Reject — decline the changes with a reason; they won't go live.
  • Cancel — withdraw a request (for example, if it's no longer needed).

Who can approve​

Approval permissions are governed by your team's roles. Typically team and site admins act as approvers, while creators submit requests.

Next steps​