> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/settings/workflow-stages.md).

# Workflow stages

Customize the workflow stages of each object type in Dastra: add, reorder, set the internal status and delete.

{% hint style="info" %}
**Workflow stages vs workflow rules**

Workflow stages define the statuses that objects move through. To automate actions when a stage changes (send a notification, create a task…), see [Workflow rules](https://doc.dastra.eu/en/features/settings/workflow-rules.md).
{% endhint %}

## Purpose of workflow stages

Workflow stages model a work process: objects move from one step to the next. You can break down your compliance procedures in an operational way by defining the stages to follow directly in Dastra.

Each object type has its own set of configurable stages:

* Data subject requests
* Data breaches
* Tasks
* Processing activities
* Assets
* Stakeholders
* Data fields
* Security measures
* Categories of data subjects
* AI systems
* Contracts

Each stage is linked to an **Internal status** that depends on the object type. For a processing activity, for example, the statuses are "draft" and "published".

## Customize workflow stages

In the side menu, click **Workspace settings**, then, in the **Process** section, click **Workflow stages**. This page is reserved for users who are allowed to manage advanced settings.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0d8971d619c271ebe14bc15ebf8b0ba1467d452b%2Fsettings-workflow-stages-1.png?alt=media" alt="The Workspace settings menu with the Workflow stages entry"><figcaption><p>The Workflow stages entry in the workspace settings</p></figcaption></figure>

Choose the object type in the list at the top of the page: you see the stages available for that process, with their internal status. Customize them to match your organization's processes, then click **Save changes**.

* **Edit** a stage to change its name, its description or its internal status, and to reserve the edition of the object in this stage to users with a specific role.
* **Add a step** to create a new one.
* Drag and drop a stage to change the order. The first stage is marked **Initial** and the last one **Final**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-c831a96254da66b4ae4b6ad57a74a2c16c133e1e%2Fsettings-workflow-stages-2.png?alt=media" alt="List of the stages of the processing activity workflow"><figcaption><p>The stages of the processing activity workflow</p></figcaption></figure>

## Delete a workflow stage

To delete a stage, click **Delete** next to it, then confirm.

Any objects currently attached to the deleted stage are automatically reassigned to the first stage with the same internal status.

For example, if you delete the "In progress" stage in the task workflow:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-2a331747273efcab27202cdd6739a8daef3e6e90%2Fsettings-workflow-stages-3.png?alt=media" alt="Task workflow with four stages"><figcaption><p>The task workflow before deleting the "In progress" stage</p></figcaption></figure>

Objects attached to it move to the first stage with the same status, for example "Needs info":

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d6be050eea59644cbb970759c050637ce0e83266%2Fsettings-workflow-stages-4.png?alt=media" alt="Task workflow with three stages"><figcaption><p>The task workflow after the deletion</p></figcaption></figure>


---

# 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://doc.dastra.eu/en/features/settings/workflow-stages.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.
