Content Approval Pipeline

This guide explains how to manage the lifecycle of content changes, from drafting in a safe environment to final approval and merging.

Overview

The content approval pipeline allows you to:

  1. Create a Changeset (an isolated draft environment) for your edits.
  2. Assign review tasks to team members.
  3. Automate the approval process when criteria are met.
  4. Merge approved content into the live catalog.

[navigate:/changesets|Changesets|git-branch]

Creating a Changeset

To start working on content updates without affecting the live site, create a new changeset.

1. Click the **Main Data (Live)** (or current changeset name) button in the top toolbar.
2. Select **Changesets (Safe Testing)** from the options.
3. Click the **Add changeset** button.
4. Enter a **Name** for your update (e.g., "Spring Catalog Update").
5. Optionally, add a **Description**.
6. Click **Save**.
7. Select your new changeset from the list to enter the isolated editing environment.

[badge:Changeset|warning] You are now working in an isolated environment. Your changes will not be visible to customers until merged.

Assigning Review Tasks

Once you have made your changes, assign a task for review.

[navigate:/changesets|Changesets|git-branch]

1. Navigate to the **Changeset Detail** page (click **View Detail** on the changeset selector or use the route).
2. Open the **Tasks** panel.
3. Click **Add Task**.
4. Enter a description (e.g., "Review price changes for Spring Catalog").
5. Select the **Assignee** (e.g., "Content Manager").
6. Click **Add Task** to save.

Automating Approval

You can set up an automation to approve changesets when they meet specific criteria.

1. Navigate to the **Changesets** list.
2. Select the target changeset(s).
3. Click the **Mass update** button in the toolbar.
4. Set the **Status** field to **APPROVED**.
5. Click **Save as automation**.
6. Name the automation "Approve Ready Changesets" and click **Save**.

Merging Approved Content

Merging applies your changes to the live production environment. You can automate this step for approved changesets.

1. Open the **Mass Update** dialog on the Changesets list.
2. Switch to **AI Mode** (if available) or use the standard editor.
3. Enter the prompt: "Merge changesets with status APPROVED".
4. Click **Save as automation** and name it "Auto-Merge Approved".

**Tip:** You can also manually merge a changeset by clicking the **Apply** button in the changeset selector dialog.

Verifying Completion

When the merge automation runs, you should receive a notification.

1. Run the "Auto-Merge Approved" automation.
2. Check the **Notification Center** (Bell icon) in the top right.
3. Look for a confirmation message: "Changeset 'Spring Catalog Update' has been merged".

**Merge Conflicts:** If a changeset contains conflicts (e.g., the same record was modified in Live), the merge will fail. Use the **Advanced Filter** to identify and resolve conflicts before retrying.