> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.md).

# Publishing a Workflow Version

When you publish a workflow, it becomes available to AccessNow end users for making requests. In other words, publishing a workflow makes it visible in the **Make a Request** dashboard. For system-initiated workflows, publishing them makes the workflows accessible in the AccessNow configuration dropdown menus.

{% hint style="info" %}
A single workflow version can be published at a time. Once published, it **cannot** be [deleted](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/deleting-or-disabling-a-workflow.md) or [edited](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/editing-a-workflow-version.md). To make changes to a published workflow, first [Create a Copy](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/workflow-version-management.md#creating-a-new-workflow-version).
{% endhint %}

You can publish a workflow **from both the Workflow Builder module sidebar and the Workflow Editor screen** once you have completed your changes. Please note that publishing a workflow means you can no longer modify that version.

To publish a workflow version **from the Workflow Builder** module sidebar:

{% stepper %}
{% step %}

### Go to the Workflow Builder Module

Click on the Workflow Builder menu item.
{% endstep %}

{% step %}

### Select a workflow record

It opens a sidebar with workflow details.
{% endstep %}

{% step %}

### Under the Version History section Actions, select Publish

Choose the desired version of the workflow to publish in the **Version History** section. In the **Actions** column, click the **three dots** icon and select **Publish** from the menu.

{% hint style="info" %}
It is recommended to [test the workflow](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/testing-a-workflow-version.md) before publishing.
{% endhint %}

This makes the workflow version available to end users in the **Make a Request** dashboard. It also prevents further editing by putting the workflow in read-only mode. To make changes, you must [create a new version](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/workflow-version-management.md#creating-a-new-workflow-version).

{% hint style="warning" %}
Publishing workflows with evaluation errors or those that do not meet specifications is not verified at the time of workflow publication. Therefore, it is crucial to thoroughly [test](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/testing-a-workflow-version.md) the workflow before publishing.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/bZ3YbeaYPiUVcfPfTUVb" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Alternatively, Publish the Workflow Directly from the Workflow Editor

You can also publish the workflow directly from the **Workflow Editor** window after finalising changes. Details on how to use it are available in the instructions for [creating a new workflow](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/creating-a-new-workflow.md) and [editing a workflow](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/editing-a-workflow-version.md).
{% endstep %}
{% endstepper %}

## **Controlling Published Workflow Visibility**

Workflow visibility settings apply only to workflows that are already published. They determine which users can see and use the workflow in the **Make a Request** dashboard. This allows you to restrict workflow access to specific individuals. Please note that it is controlled on a per-individual basis.

### **How to Control Published Workflow Visibility**

In the **Workflow Management** module, under the **Visibility tab**, you can control workflow visibility.

* **General**: You can make the workflow visible to all users in the Make a Request dashboard by using the General visibility setting. To restrict access, use the **Exclude Users** option to prevent selected users from seeing it. Currently, there is no option to set visibility by user groups.

<div data-with-frame="true"><figure><img src="/files/fcNttRjd79J6gy6RAIZs" alt="" width="511"><figcaption></figcaption></figure></div>

* **Restricted:** Restricted visibility limits workflow access to only the selected users. Use the **Authorized Users** list to grant specific individuals access to the workflow in the Make a Request dashboard. Currently, there is no option to set visibility by user groups.

<div data-with-frame="true"><figure><img src="/files/bSZW9asghxyj8Ew1xLb5" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.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.
