> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/versions.md).

# Versions

Review changes, compare versions, and publish a Sagent release.

The **Versions** section gives you control over Sagent releases. It separates draft changes from the live experience, so you can review updates before shoppers see them.

Use it to preview, publish, unpublish, or restore a version when needed.

Use **Versions** to track each Sagent release. Every version shows when it was created, who created it, when it was published, and its current status.

<table data-header-hidden data-full-width="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Publish your Sagent</strong></td><td>To publish a version of your Sagent, navigate to the Versions tab in your settings. Click the three-dot menu next to the desired version and select Publish. Before publishing, you can use the Preview in app button to review your Sagent.</td></tr><tr><td><strong>Create a New Version</strong></td><td>Once a Sagent is published, any modifications automatically create a new draft version. After making your edits, return to the Versions tab, click the three-dot menu next to the latest draft, and select Publish to apply the changes.</td></tr><tr><td><strong>Unpublish the Sagent</strong></td><td>To remove your Sagent from your website, access the Versions tab, click the three-dot menu next to the currently published version, and select Unpublish. This will take it offline until you choose to republish.</td></tr><tr><td><strong>Revert to a Previous Version</strong></td><td>If you need to revert to an earlier version, go to the Versions tab, locate the version you want to restore, click the three-dot menu, and select Publish. This will make the selected version live.</td></tr><tr><td><strong>Preview a Version</strong></td><td>To view any past version, navigate to the Versions tab, click the three-dot menu next to the version you want to check, and select View version. This opens a read-only view. To return to an editable version, select return to latest version.</td></tr></tbody></table>

### Release states

The status chip shows the version's live state:

* **Draft** contains changes that shoppers cannot see yet.
* **Published** is the version currently available to shoppers.
* **Unpublished** is offline and unavailable to shoppers.

After publishing, later changes create a new draft. This keeps the published experience unchanged while you prepare the next release.

### Publish a version

{% stepper %}
{% step %}

#### Open a version

Open **Versions** and expand the version row. The version list shows its number, creator, creation date, publication date, and status.
{% endstep %}

{% step %}

#### Review the changes

Review the changes included in the version. Each entry identifies whether an item was added, changed, or removed.

Select another version from **Compare version with** to inspect the difference between releases. The comparison shows the full change list between the two selected versions.

Use the visibility control to show or hide an individual change while reviewing. It does not include, exclude, or alter that change in the published version.
{% endstep %}

{% step %}

#### Add a release message and publish

For a version available to publish, describe the release in **Version Message**. This field is optional. Select **Generate message** to create a draft message, then review it before publishing.

Before publishing, confirm:

* the preview works for each relevant shopper journey;
* catalog, knowledge, and translations are current and synced;
* the comparison contains only approved changes.

Select **Publish version** when the changes are ready for release.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Check the status chip before making changes. A version can be **Draft**, **Unpublished**, or **Published**.
{% endhint %}

### Version details

Expand a version to see its change list. Entries identify the changed area, such as **General**, **Guidance**, **Tags**, or **Localization**.

The comparison view highlights differences between the selected versions. It is a review tool. It does not merge changes or create a partial release.

### Restore a previous version

Publish a previous version to make its complete recorded configuration live again. This is a full rollback, not a selective reversal of individual changes.

Use **View version** to inspect an earlier version before restoring it. Earlier versions open read-only. Return to the latest version to make new edits.

{% hint style="warning" %}
Review the complete older version before publishing it. It can restore all of its previous configuration, including settings you did not intend to change.
{% endhint %}

### Frequently asked questions

<details>

<summary>What does a version status mean?</summary>

A **Draft** is not live. A **Published** version is live. An **Unpublished** version is offline.

</details>

<details>

<summary>Do I need to write a version message?</summary>

No. Version messages are optional. Add one when it helps teammates understand the release.

</details>

<details>

<summary>How can I check what changed between releases?</summary>

Expand a version and select a release from **Compare version with**. Review the resulting change list before publishing.

</details>

<details>

<summary>Can I roll back one change from a version?</summary>

No. Publishing an earlier version restores that full version. Create a new draft for selective changes.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/how-to-guides/sagent/versions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.