Changes and reviews

Catalyst requires users to expressly publish any changes to workflows, skills, and other resources. All updates made within a chat are grouped into a change set, which can be published directly or proposed for review depending on your team settings.

---

​

Change sets

A change set collects every resource Catalyst modified in a chat session: workflows, help desk skills, Catalyst skills, dashboards, and more. You can view the change set in the collapsible changes slip above the chat composer. Until you publish (or a review is approved and published), changes exist only as drafts tied to the chat session.

​

Review CI policy changes

Catalyst can stage your team’s Review CI settings as a portable resource. Where Review CI is enabled, choose Open resource → Review CI policy to view required workflows and evaluation suites. In a Catalyst session, you can stage changes to these checks and inspect additions and removals before proposing or publishing them. Team managers can also choose these checks from Test & Release → Reviews → Required checks. Each configuration review runs the policy it captured when the review was created. The review’s check list links to the resulting workflow or evaluation-suite run so reviewers can inspect the evidence before publishing.

​

Publishing and discarding individual changes

You don’t have to publish an entire change set at once. When approval isn’t required, you can publish or discard individual changes from the changes slip above the composer, or from a resource’s own tab. Publishing a change also applies any drafts it depends on; discarding one also discards the drafts that depend on it, so the change set stays consistent.

---

​

Direct publish vs review

Which path you use depends on the Catalyst review approval settings. Team managers can open Settings → Catalyst → Approval settings → Catalyst to configure the policy. Teams that use Test & Release can also open Test & Release → Reviews → Approval settings → Catalyst.

• If Require approval before publishing is off, users with Builder permissions or higher can directly publish changes drafted by Catalyst.
• If Require approval before publishing is on, users with Builder permissions or higher must propose the change set for review. Designated approvers must sign off before anyone can publish.

---

​

Team settings for reviews

Managers can configure review behavior under Settings → Catalyst by clicking Approval settings. The same action is available under Test & Release → Reviews when Test & Release is enabled. The Approval settings dialog separates the policies for Catalyst and Incoming promotions. Select Catalyst to configure publishing approvals for Catalyst changes. Select Incoming promotions to configure approvals for configuration received through Team Links. Each policy has its own requirement toggle and approval steps.

​

Require approval before publishing

When enabled:

• Builders must propose change sets for review rather than publishing directly from the chat.
• Configured approvers must approve or deny each review.
• After approval, an authorized user clicks Publish on the review to apply the change set.

When you require approval before publishing, configure at least one approver step, which can consist of users, groups, or special members like Team owners. Click Save changes after editing approvers.

---

​

Propose for review

When approval is required and you have pending changes:

1. Finish staging changes: Confirm every resource in the change set shows the state you expect.
2. Click Propose for review: In the collapsible bar above the composer, click Propose for review.
3. Add title and description: Enter a short title (required) and optional description explaining what changed and why. Click Propose.
4. Notify reviewers: The review appears in the Reviews view of the Catalyst page for teammates with access. They can inspect changes without opening your private chat (unless you shared it as a team chat).

Each pending change set can have one review. If you keep editing after proposing, coordinate with reviewers. They approve the change set as it stood when the review was created.

---

​

Reviewer workflow

Slack change set approval messages show the Target environment, so you can check where the changes will apply before approving. When email notifications are enabled, designated approvers receive a Promotion approval email for promotions between environments, or a Change set approval email for Catalyst changes. The email includes the review title, a summary of up to 500 characters, requester, and resource count. Promotion emails show the configured source and target environment names. Click Open review to read the full description, inspect the changes, and approve or deny them in Serval.

1. Open the Catalyst page from the sidebar and switch to the Reviews view. Reviews show a title, proposer, linked resources, and status.
2. Select a review to see title and description (editable by reviewers with access), Catalyst session link that opens the originating chat if you have access, per-resource diffs (workflow code changes, skill content, etc.)
3. Approve or deny the review

When all required approvers have signed off, the review shows Approved. Someone with publish permissions can now click Publish on the review to apply the change set.

---

​

After publishing

• Resources show as Published in the originating chat session
• Workflows appear in Workflows, skills in Skills, and dashboards in Analytics
• The review status updates to Published

If something fails while you’re publishing, check the review detail for errors. Fix the underlying issue in Catalyst and propose a new review if needed.

---

​

Related