Review and approval
So nothing gets published without someone approving it: how to turn it on, how to send a description for review and what the approver does.
What it is
Publishing a description is what sends it to your downloads, your channels and the API. Normally, what you generate is published on its own. With the «Editorial workflow» on, nothing new is published until an administrator approves it, and what was already published stays the same in the meantime.
Everything goes by product and language: approving the English one doesn't touch the Spanish one.
How to turn it on
In Content → «Brand voice», the «Editorial workflow» switch. An administrator changes it. Turning it off doesn't empty the queue: what was left pending can still be approved, and new content goes back to publishing on its own.
A description's states
On the product page, the «Editorial state» section says where each language stands:
| State | What it means |
|---|---|
| «Not published» | There's a new version, and nothing has been published in that language yet. |
| «Published · pending changes» | What's published keeps going out, and a newer version is waiting. |
| «In review» | Someone sent it for review: it's in «Waiting for approval». |
| «Published» | It's what goes out in your downloads, channels and API. |
From a new version to published
- You generate or translate: the new version waits, unpublished.
- Someone with the Editor role or higher clicks «Send for review» on the product page. Until then it doesn't show in the queue.
- The description shows in Content → «To publish», the one that has waited longest first.
- An administrator clicks «Approve and publish» or «Reject».
The queue
Each row is a product in one language, with signs to help you decide: «Replaces what's live» or «First publication», «QA found problems» and how many claims there are to review. If QA flagged something, approving requires ticking «Publish anyway».
The queue belongs to the organization: a supplier, or someone with access limited to part of the catalog, doesn't see it.
Reject with a reason
When rejecting, you can write the reason and click «Reject and notify»: it goes into the product's comments and the person who generated the version gets a notification. «Reject without a reason» just sends it back. Either way, the version goes back to draft and what's published stays the same. Until someone touches the product page, it says «Rejected · see reason».
Other administrator tools
- «Unpublish» takes the description out of your downloads, channels and API in that language.
- «Go back to this version», in the history, publishes an earlier version and leaves the description «Pinned»: a new version doesn't replace it until someone clicks «Unpin».
- «Scheduled publication», on the product page: you pick a version and a date, and it publishes on its own at that time, without going through the queue. If by then a newer version is already published or the description is pinned, it isn't published and you get a notification.
Follow-up
Reports has «Pending approval» and «Publications and rejections». The PDF quality report counts the descriptions in review when the workflow is on.