In businesses where several people prepare content, the Content approval add-on makes sure editors’ changes don’t reach the screens until an admin approves them. The add-on is included in V-Premium; on other plans turn it on from the Add-ons page.
What needs approval?
- Changes by someone with the Editor role to a live playlist (items, durations, name, shuffle).
- Every change an editor makes to the schedule rules.
When the change is saved, screens keep playing the current version; the editor sees a “sent for approval” notice. A playlist that isn’t used by any screen or rule yet is edited directly, because it can only reach screens through an approved schedule or an admin’s change.
While approval is on, editors can’t delete a live playlist or change a screen’s default playlist; admins do that. Uploading media and sending emergency alerts don’t need approval.
The account owner, admins and API keys publish directly.
Approving
- When a change awaits approval, admins get an email and a mark appears next to Approvals in the menu.
- On the Approvals page each request shows the “Live now” and “Proposed” versions side by side.
- Approve and publish sends the change to the screens right away; Reject lets you add an optional note.
- The editor gets an email with the decision.
If the live version changed after the request (e.g. an admin edited the same playlist), the request shows a “stale” warning; approving overwrites that change.
For editors
- Saving the same playlist again updates your pending request; no new request is opened.
- On the Approvals page you only see your own requests and can remove a pending one with Withdraw.
Still have questions? Write to us