Skip to main content
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 bar above the chat composer. Until you publish (or a review is approved and published), changes exist only as drafts tied to the chat session.

Direct publish vs review

Which path you use depends on your Catalyst settings (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.
When approval is required, per-resource Publish buttons are hidden. Publishing happens only after a review is approved and someone clicks Publish.

Team settings for reviews

Managers can configure review behavior under Settings → Catalyst.

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.
Leave approval off for small teams that trust every builder to publish. Turn it on when changes need a second pair of eyes before they go live.

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 under Catalyst → Reviews 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

  1. Open Catalyst → Reviews from the sidebar. 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.

Catalyst overview

What Catalyst can do

Catalyst workspace

Get familiar with the Catalyst interface

Getting started

Enable Catalyst, open your first session, and publish a change

Tutorial

Using Catalyst to analyze ServiceNow tickets and build automations

Building workflows

Natural language prompting, manual edits, versioning

Dashboards

Building analytics dashboards with Catalyst