Approvals and content versions

Pushwoosh saves a new version every time you save a push preset or email template, for every account. Content approval adds a review step on top of that. While it’s on, a version can’t be sent until a reviewer approves it.

Nota

Versioning and approval cover push presets and email templates only. SMS, in-app, LINE, and WhatsApp content have no version history and aren’t affected by this restriction.

View, compare, and restore versions

Every push preset and email template keeps its last 20 versions in its version history, available whether or not content approval is on for your account. A version that’s waiting for approval is never evicted, even past the 20-version limit.

From the push content editor, open the version history to:

• Compare two versions side by side to see what changed between them.
• Restore an earlier version. This fills the text of that version into the editor, but media, actions, and settings stay as they are. Nothing is saved until you click Save.

Nota

Push presets and email templates that existed before content approval shipped got a v1 version created for them retroactively, already approved.

Turn on content approval

Without content approval, every saved version is automatically approved, so content keeps sending as before. To require review before sending, ask Pushwoosh support to turn on the Require content approval restriction for your account. It has no self-service toggle.

Grant the Approve messages permission

Reviewers need the Approve messages permission to see the review queue and approve or reject submitted versions. Add it to a role from Users and roles, in the same Messaging permissions group as Send messages and Delete messages. See Available permissions for the full roles matrix.

Submit content for approval

Once content approval is on, the editor shows a version status chip next to Save: Draft, On approval, Approved, or Rejected.

To submit a version for review, click Submit for approval next to Save. The chip changes to On approval, and the version appears in the reviewer’s queue.

Nota

A reviewer can’t approve or reject their own submission. Have a different user with the Approve messages permission review it.

If a reviewer rejects it, the chip changes to Rejected and shows the reviewer’s reason on its second line. Edit the content and click Submit for approval again to resubmit.

Editing approved content starts a new draft

Editing a push preset or email template that’s currently Approved moves it to Draft, with a version number next to the status, for example Draft · v4. Editing also cancels any other request still waiting for approval on that content.

Review pending approvals

Reviewers work from the Pending approval tab on the Push presets list. A badge on the Content → Push Presets menu item shows how many versions are waiting for review.

For each pending version, a reviewer can:

• Compare it against the previous version to see what changed.
• Approve it, so it becomes sendable.
• Reject it with a reason. The reason is required, and appears both on the preset’s card in the list and on its status chip in the editor.

Nota

Submitting a version doesn’t send the editor or reviewer an email. The pending-approval queue and the menu badge are the only places the request is visible, so check them directly rather than waiting for a notification.

Sending is blocked until content is approved

With content approval on, you can’t send a push preset or email template version that isn’t Approved. This applies everywhere a send can start:

• The one-time push form lists unapproved presets in the dropdown but keeps them unselectable, and rejects the send with error code 2080.
• A Customer Journey element sending unapproved content stops there, also with error code 2080.
• The deprecated createMessage JSON API method rejects the request with error code 210.

All three come back with the message Preset content is not approved.

The one-time push form also restricts creating and testing content

With content approval on, the one-time push form no longer offers Create new. Submit and approve the preset from Content → Push presets first, then select it from the dropdown. The push content editor also hides Test push notification entirely, regardless of the preset’s version status.