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 creates, updates, or unpublishes a data item, 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 proposed change, to determine what is changing. For a CREATE, only proposedDataItem is present. For an UNPUBLISH, only currentDataItem is present.
5. 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, and submittedByUserId.
3. Transform the data into your external system's format.
4. Send the transformed record to your external system.