> 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/about-the-workflow-designer.md).

# About the Workflow Designer

The Workflow Designer is a powerful process and form modeling web application intended for use with your Collibra platform.

The Workflow Designer is available on regional GCP and AWS clouds, including gov-cloud environments for eligible customers.

All of your Collibra environments share a Workflow Designer. For example, if you have 3 Collibra environments, all 3 environments would use the same Workflow Designer.

When you publish a workflow from a Workflow Designer that is shared between multiple environments, the workflow is published to the environment you used to access the Workflow Designer.

{% hint style="success" %}
If you have multiple Collibra production environments, and require more than one Workflow Designer, contact your Collibra Account Team or [Collibra Support](https://support.collibra.com).
{% endhint %}

## Promote workflows

Develop and test workflows in your development environment first. Use the [Collibra migration feature](https://productresources.collibra.com/docs/collibra/latest/Content/Settings/Migration/to_migrating-model-objects.htm) to selectively move one or more workflows to a higher environment, such as production.

By using the migration feature, you can continue to evolve your workflow since changes in development do not affect production until you migrate the workflow.


---

# 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/about-the-workflow-designer.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.