> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/project-configuration/workflow-configuration.md).
# Workflow configuration
Easily activate, modify, or deactivate project workflows with our intuitive configuration tool. Enjoy streamlined setup, clear status updates, and flexible management for all item types.
We’ve completely rebuilt the **Workflow** and **Global Rules** configuration to offer a more intuitive and powerful experience. Whether you're setting up workflows for the first time or refining complex processes, this update simplifies everything — visually and functionally.
### Activating Workflow
To activate workflow for a specific item type, click 'Get started' button.
Once the Workflow is added, it becomes associated with your project item type and can be modified or deactivated later.
### 📴 Deactivating Workflow
You can **deactivate** a workflow, but not delete it. When deactivated:
* Rules and transitions remain visible but inactive
* Configuration is **read-only**
* A clear **status message** is shown
* You can **re-enable** it at any time
When you deactivate workflow, then both **Global rules** and **Transitions are deactivated.**
---
# 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://docs.aqua-cloud.io/documentation/project-configuration/workflow-configuration.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.
