> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Sample Flows

## Article: Sample Flows

## Article Link: https://dev.wix.com/docs/api-reference/account-level/enterprise/cms-compliance/compliance-review-request-v1/sample-flows.md

## Article Content:

# 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](https://dev.wix.com/docs/api-reference/account-level/enterprise/cms-compliance/compliance-review-request-v1/review-requested.md) webhook.
1. When a user creates, updates, or unpublishes a data item, the CMS host calls [Request Review](https://dev.wix.com/docs/api-reference/account-level/enterprise/cms-compliance/compliance-review-request-v1/request-review.md), and you receive a Review Requested event.
1. Read the `action` to see what the user did.
1. 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.
1. 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](https://dev.wix.com/docs/api-reference/account-level/enterprise/cms-compliance/compliance-review-request-v1/review-requested.md) webhook.
1. On each event, extract the `complianceReviewRequest` object, including the `action`, `currentDataItem`, `proposedDataItem`, and `submittedByUserId`.
1. Transform the data into your external system's format.
1. Send the transformed record to your external system.