CMS Compliance: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

Review CMS content changes for compliance

When a user changes content, you can review the change before deciding whether it should stand. The review request gives you both the live version and the proposed version, so you can see exactly what is changing.

To review a content change:

1. Subscribe to the Review Requested webhook.
2. When a user submits a publishing or unpublishing workflow, the CMS host calls Request Review, and you receive a Review Requested event.
3. Read the action to see what the user did.
4. Compare currentDataItem, the live version, with proposedDataItem, the version submitted for approval. For PUBLISH_DRAFT, only proposedDataItem is present. For UNPUBLISH_PUBLISHED, only currentDataItem is present.
5. For UNPUBLISH_CHANGED, read versionOnUnpublish when present to determine whether the user requested to preserve the latest draft edits or the live published version.
6. Apply your review decision in your own system, using submittedByUserId and submittedAt to record who submitted the change and when.

Forward content changes to an external compliance system

If you maintain an external audit or compliance system, you can keep it in sync with every reviewable content change on the site.

To forward content changes to an external system:

1. Subscribe to the Review Requested webhook.
2. On each event, extract the complianceReviewRequest object, including the action, currentDataItem, proposedDataItem, optional versionOnUnpublish, and submittedByUserId.
3. Transform the data into your external system's format.
4. Send the transformed record to your external system.