> 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/enable-or-disable-workflows.md).
# Enable or disable workflows
You can enable or disable workflows from the workflow definitions table or from the individual workflow definition pages.
You must have the Sysadmin global role or a global role that has at least the Workflow Administration global permission to perform this action.
{% tabs %}
{% tab title="Definitions table" %}
{% stepper %}
{% step %}
On the main toolbar, click 
→ 
**Settings**.\ :chevrons-right: The **Settings** page opens.
{% endstep %}
{% step %}
Click **Workflows** → **Definitions**.
{% endstep %}
{% step %}
At the end of the row, click 
or 
to respectively enable or disable a workflow.
{% endstep %}
{% endstepper %}
{% endtab %}
{% tab title="Definition page" %}
{% stepper %}
{% step %}
On the main toolbar, click → **Settings**.\ :chevrons-right: The **Settings** page opens.
{% endstep %}
{% step %}
Click **Workflows** → **Definitions**.
{% endstep %}
{% step %}
Select the workflow you want to enable or disable.
{% endstep %}
{% step %}
At the right of the title bar, click or to respectively enable or disable the workflow.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}
---
# 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/enable-or-disable-workflows.md?ask=&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.