What this page is for
Maya submitted the homepage hero. This page is Priya's side of that, and the moment someone publishes the copy she approved. The reason there is a copy at all is on Approvals. What Maya clicked is on Submitting for approval.
You see Production requests if you are a Production approver, or if you can publish to Production. Staging is its own list. Managing the team does not open the queue. If you are neither an approver nor able to publish there, the Approval Requests card is not on the environment home, and the requests page says Production approval requests are not available to you. Staging uses the same sentence.
There is no email. Open the project and look at the card. The count under the title reads like "Production: 2 waiting · 1 approved." No open requests means the queue for that environment is clear. The card stays up while approvals are on, or while something is still open after you turned them off.
Find the hero
- On the environment home, open Approval Requests. Click Production requests or Staging requests. The page title is Approval Requests, with the same two tabs as settings. A request belongs to one environment, so the review itself has no second tab.
- Waiting for approval lists requests that are not ready yet. Each row is the widget or the collection, its name, who submitted it and when, the note, and progress such as 1 of 2 approvals. Your response shows whether you already approved.
- Approved — ready to publish lists requests that have met the minimum. The green Approved pill sits next to Publish when you can publish. If you can only approve, you see the pill and not the button.
- Recently closed is collapsed. Open it for published, rejected, withdrawn, and replaced requests, newest first. It loads more as you go.
Waiting requests are oldest first, so the hero Maya submitted this morning is above the one she submitted after lunch. Click the row to open the review. The same Approval Request card on the hero's Publish tab links here with View request, if you are allowed to see requests.
Read what you are approving
The header names the hero, says Widget or Collection, names the environment, and shows who submitted it and when. Maya's note is labeled Note. A tag, if she added one, is here too. The status pill and the progress sit with every decision so far: who, when, and the comment.
Preview is what a publish would put live. It is the frozen hero, rendered, with the device tabs you already use in the composer. For a shared collection that is already live, the preview uses that live version, including the collections inside it. A note names those collections: this publish keeps the live version, and to change one you submit that shared collection for approval.
Compare with live puts Submitted beside what Production serves today. Visual is the two renders. JSON is the two structures. Under that, a summary says what changed in the hero itself, then each collection as Added, Removed, Changed, Unchanged, or Already live — this publish keeps the live version.
The first time this hero would go live, there is nothing to put on the right. The page says it has not been published in Production yet, and this will be its first publish. You get the preview, not an empty comparison.
Compare describes a publish as of when you opened it. If someone publishes the product card while you still have the hero's review open, refresh before you approve. The card may have moved from "part of this request" to "already live." That rule is on Submitting for approval.
Approve, reject, or withdraw
Approve and Reject show only if you are an approver, the request is still open, and you have not responded. Each opens a dialog titled with the hero's name.
- Approve Homepage hero? says your approval counts toward the number it needs before it can be published. Comment (optional) allows 1000 characters. The help text says the submitter and the other approvers see it. Confirm with Approve.
- Reject Homepage hero? says rejecting closes this request, so it cannot be published, and whoever submitted it can submit it again. The same optional comment. Confirm with Reject. A rejection is final for this request. You cannot switch it to an approval afterwards. Maya fixes the draft and submits a new one.
You can approve a request you submitted. If the minimum is 2, your approval is one of the two. It does not finish the request by itself. Approving a second time is refused: you already responded.
Withdraw shows if you submitted the request, or if you can publish in this environment. The dialog is Withdraw this request? Withdrawing closes it without a rejection. Nothing from it will be published. An approver who did not submit it, and who cannot publish, does not see Withdraw. Use Reject when the copy is wrong. Use Withdraw when the request should simply go away — Maya changed her mind, or the campaign was pulled.
Only an open request can be approved, rejected, or withdrawn. A closed one — published, rejected, withdrawn, or replaced by a newer submit — keeps its history and takes no new decision.
Publish the approved copy
When the progress meets the minimum, the pill turns green: Approved. Publish sits next to it, on the review, on the requests list, and on the hero's Approval Request card. You need Post Publish To Production or Post Publish To Staging. Being an approver is not that permission. Priya can approve all day and still not see Publish.
- Click Publish. Confirm. This is the same publish a Publish Now would have been, except the source is the frozen copy.
- The request moves to Publishing while it runs. A second click from someone else is told the request is already being published.
- On success, the snapshot is versioned the way Publishing describes. The first one is 1.0.0. The tag Maya entered is on that version. The live site fetches this snapshot, not her later draft.
If the publish fails, the request returns to Approved and the page says the last publish failed, with the reason. Try again. The frozen copy is still the copy. If the page stays on Publishing for more than ten minutes, publish again. A publish that never finished can be tried after that.
Publishing a shared collection from its own request updates every live widget that references it. Publishing the hero does not republish a shared collection that is already live. Both of those are the same rules as a publish without approvals.
The first publish of a widget still has to fit the plan. If it does not, Publish is refused and the request stays approved.
What you might see
| You see | What it usually means |
|---|---|
| 1 of 2 approvals, after you were sure it was 2 | Someone left the approver list, left the team, or the minimum went up. Only people who are approvers right now are counted. |
| You have already approved or rejected this request, and a decision cannot be changed | You responded already. The comment stays as you wrote it. A new submit is a new request, and you can respond to that one. |
| This request was rejected, so it cannot be published | Jordan closed it. Look at the comment, change the draft, and submit again. |
| This request was replaced by a newer request for the same widget or collection | Maya submitted again. Open the new row under Waiting for approval. Approvals on the old one do not carry over. |
| This request has 1 of 2 required approvals, so it cannot be published yet | Publish was clicked too early, or an approval stopped counting. Wait for the second approval. |
| Someone is publishing this request right now | Someone else clicked Publish. Read it again in a moment. If it failed, it returns to Approved and says the last publish failed. |
| Production approval requests are not available to you | You are on the team, and you are not a Production approver, and you cannot publish there. Staging uses the same sentence with Staging. Ask the person who manages Approval Settings to add you, or ask for Post Publish To Production or Post Publish To Staging. |
After it is live
The published hero is an ordinary snapshot. Tokens, the published key, and cache refresh are unchanged. Those are Publishing, Projects, Environments & Tokens, and Widget Caching.
History shows the version this request created. While approvals stay on, you do not republish an older row in place. Restore it to the draft and submit that. Restore to draft itself is never blocked. The habit is on History, compare, and restore.