> 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/status-and-transitions.md).
# Status and transitions
Easily add, delete, and manage workflow status transitions. Set role-based and advanced rules, use “ANY” transitions, and monitor rule indicators for precise project workflow control.
#### ➕ Adding Transitions
You can add transitions in two ways:
* **Drag & drop** from one status node to another
* Click **“Add Transition”** and select statuses
**Note:**
* Transitions open a sidebar only after being created.
* Transitions **cannot be edited**, only deleted and re-added.
* Delete transitions using the keyboard **Delete** key or the **sidebar icon**.
#### ⚡ Special Transition Type: **ANY**
Add a transition that applies to or from *any* status:
* **From \[status] → ANY**: move from one status to any other
* **From ANY → \[status]**: move from any status to one defined status
This is visually represented by special nodes on the graph.
### Transition Rules
In the **sidebar**, you can define two types of rules per transition:
#### **Status Transition Rule** (only one allowed)
Defines **which roles** can move an item from one status to another. Default is **Any role**.
#### **Advanced Rules** (multiple allowed)
Set field behaviors per role when the transition occurs. You can:
* Add/remove rules anytime
* See rule count directly on the transition arrow
* Edit or delete existing rules
**Attributes of advanced rules:**
* **Field** – The field being impacted
* **Has Attribute** – What’s applied (e.g., Required, Read-only, Default Value)
* **Mode** (if applicable) – Define default value or empty state
* **For / Role** – Specify which roles are affected
* **Value** – Whether rules apply or not
Went there is at least one rules applied to Transition, then there is an indicator on the arrow, that shows that there are some rules.
---
# 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/status-and-transitions.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.
