> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/managing-workflows-in-collibra/view-and-edit-workflows.md).

# View and edit workflows

You can view both the XML schema and a visual representation of the workflow definition in Collibra Platform.

You must have the Sysadmin global role or a global role that has at least the Workflow Administration global permission to access this page:

{% stepper %}
{% step %}
On the main toolbar, click <img src="https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-c495609e46095abc7bbc4b08bd4d0e0beebb917a%2FProductsIcon.svg?alt=media" alt="Products icon" data-size="line"> → <img src="https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-268a786d787f353b92e094a60945df32bf9cb208%2FCogwheelIcon.svg?alt=media" alt="Cogwheel icon" data-size="line"> **Settings**.\ <i class="fa-chevrons-right">:chevrons-right:</i> The **Settings** page opens.
{% endstep %}

{% step %}
Click **Workflows**.\ <i class="fa-chevrons-right">:chevrons-right:</i> The Workflows settings page appears on the **Definitions** tab page.
{% endstep %}

{% step %}
Select a workflow.
{% endstep %}

{% step %}
In the tab pane, click **Flow**.
{% endstep %}
{% endstepper %}

![](https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-dd31fba59e6d6f4a83cf0a3ef4e84337e4fd310f%2Fexample-workflow-flow_new.png?alt=media\&token=5896ee94-356a-49fa-b1c2-5c1ff2b6da55)

The lower part of the page contains the raw workflow definition:

![](https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-cbb1a08a9a28c5bf2f2ca6b5fb94c3f80090fd73%2Fexample-workflow-xml_new.png?alt=media\&token=5540161e-4fbd-4c07-8b0d-0826c9cfad91)

To export the workflow definition as BPMN and edit it, follow the procedures described in the [Edit an out-of-the-box workflow](/workflows/edit-an-out-of-the-box-workflow.md) section of the Workflows documentation.

{% hint style="warning" %}
If the workflow was created using the Workflow Designer, edit the workflow in the Workflow Designer and [publish](/workflows/managing-workflows-in-collibra/publish-a-workflow.md) the new version to your environment.
{% endhint %}

For minor updates, you can edit the XML schema directly:

1. Click **Edit** to edit the XML.
2. Click **Save** in the lower-right part of the page to save your changes and exit edit mode.

{% hint style="info" %}
The changes you make are not reflected in [currently running instances](/workflows/managing-workflows-in-collibra/view-running-workflow-instances.md) of the workflow.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/workflows/managing-workflows-in-collibra/view-and-edit-workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
