Review Content

Open Review Content

Content Bank > Review Content. The three stat tiles read straight from the queue: an unlabeled count ready to decide, In the queue (staged in total), and Needs clearing (stuck in a state that blocks regeneration). When clearing is needed, a banner explains why and that clearing never touches the product, only the queue.

Once you have decided everything waiting, the queue shows its own empty state rather than empty tiles:

Filter by state

Four chips: All, Pending (ready for your decision), Stuck mid-apply (an approval started but never finished), and Already applied (the value was written, but its queue row was left behind).

A stuck or already-applied row offers only Clear instead of Apply/Reject, which frees the field without writing or un-writing anything.

Open a row to read it

Click a row to open its detail sheet: the proposed value next to the field's current value on the product, in a Proposed value tab, plus a Record tab with the tool, how it ran (manual or automated), when it was staged, its state, and its queue ID. A Previous / Next stepper at the top lets you work through several items without closing the sheet each time.

When you approve or reject from inside the sheet, it advances to the next loaded item on its own; at the end of what is loaded it tells you whether that is the end of the whole queue or just the end of this page.

Approve or reject one item

Each pending row has Apply and Reject buttons, also available in the drawer's footer. Rejecting is a hard delete: the generated text is gone for good, and regenerating it costs a fresh AI request, so a confirmation always asks first ("Discard this draft?").

Applying one item is one-click, with no confirmation, whenever the write is safely recoverable: Content History is on and you are entitled to Restore. If either is not true, a confirmation appears first, titled "Replace this product's content?", and says exactly why there would be no way back: "Content History is switched off, so no restore point is recorded..." when history itself is off, or "You can restore the previous content from Content History with a Business Plan" when you have no Restore access.

When the product changed after staging

If a product was edited after an item was staged, approving it fails with a conflict instead of silently overwriting that later edit. The failure shows as a toast and as an inline note on the row itself, so it survives a 5-second toast disappearing.

Reloading the list lets you compare the proposal against the product's actual current value before deciding whether to still overwrite it.

Act on several at once

Select rows with their checkboxes (a stuck or already-applied row cannot be bulk-selected) to open the selection strip, with Select all N loaded, Clear selection, and Reject N / Apply N for the whole batch.

Unlike a single Apply, a bulk Apply always confirms first and names exactly what it is about to do, whether or not the write is protected by History and Restore:

A bulk run reports a partial outcome rather than one pass/fail verdict: each item that failed is listed with its own reason, right below the ones that succeeded.