> 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/out-of-the-box-workflow-publishing.md).

# Out-of-the-box workflow publishing

In general, when you start your Collibra Platform environment, all missing out-of-the-box (OOTB) workflows are published, enabled and configured with the default settings.

{% hint style="info" %}
OOTB workflows are not automatically updated after an upgrade.
{% endhint %}

The following list of rules applies to OOTB workflow publishing in version 5.1 or newer when you (re)start an environment:

* OOTB workflows that are missing (deleted or never published), are published, enabled and configured with the default settings.
* Published OOTB workflows are not automatically updated, even if they are not customized. To install a new version of an OOTB workflow, do either of the following:
  * Remove the existing workflow and then restart the environment.
  * Download the updated workflows from the [Community Downloads page](https://productresources.collibra.com/downloads/):
* If you created a workflow with the name of an OOTB workflow and the actual OOTB workflow is not published, the actual OOTB workflow is published, enabled and configured with a name having an **OOTB\_** prefix, for example OOTB\_Approval Process.

{% hint style="success" %}
[Disable](/workflows/managing-workflows-in-collibra/enable-or-disable-workflows.md) the OTTB workflows you do not want to use. If you delete them, they are republished when you restart the environment.
{% 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/out-of-the-box-workflow-publishing.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.