# Workflow & Assignation
## Operation
A workflow allows you to define the life cycle of a form's submissions. This functionality allows a team to follow one another on the same work at different phases.
Example:
The idea is that the cards created will be in the "Planning" state. Instead of the save button, there will be two buttons which will either allow you to stay in the current state (arrow "Save") or move to the state "In-Progress / Validation".
The status of a form is traceable by its color in list views as well as by a small insert in the form.
When a form reaches a final state ("Done", "Blocked", "Cancelled"), it is in an archived state.
It is no longer possible to modify it (except in administrator editing mode).
The transition buttons between states are configurable on the one hand for the visual appearance (icon, wording, color) but they can also be subject to conditions which allows you to define who has the right to work on a file on this state and when the button is available.
## Assignation
To do this, we will add a user field (do not activate the "multiple" option) and in the workflow tab, we will set up the assignment by selecting the user field.
So that users can access the submissions assigned to them on mobile, a button must be added in the [app configuration](/user-documentation/build/building-apps/app-configuration.md) with the following values:
* Action: My submissions
* Option chosen: Name of form with workflow and assignment
* Filters: Submissions assigned to the user
As long as the cards are assigned to the user, they will receive all updates in real time on their mobile. When a submission reaches a final state of Workflow, its assignation remains, but the submission does not count anymore in the limit of 1,000 submissions max assigned to a single user. It is possible, using an [automation](/user-documentation/build/building-forms/automations.md), to unassign automatically a submission that reaches a final state in a Workflow.
Please note assignation is not possible for forms that are not first level
## Setting up
In the form designer (or form builder), there is an option in the toolbar at the top right:
In this menu it is possible to choose from a set of predefined workflows.
When you select a workflow, you are presented with a graphical representation.
Then, for all existing transitions you can decide:
* wording
* color
* of the icon
* and a button display condition
If the condition is not checked, the button does not appear. By using [conditions](/user-documentation/build/building-forms/conditions.md) on the current user, it is therefore possible to choose who has the right to move a form from one state to another.
In addition, it is also possible to create conditions that rely on the state of the submission.
This can make certain fields active only from the moment the form arrives in the correct state.
## Advanced functions
Users with an administrator license can directly save a form without going through a workflow transition to edit mode.
### Mass update the workflow state
Similarly, an administrator can modify (mass) the state of the files without going through transitions.
To do this, you must select the cards in the [table view](/user-documentation/use/views/table.md), then **Actions > Modify**.
After selecting the "Mass Edit" button, a new window allowing you to choose the field to modify is displayed. Click on the "**Field to update**" then from the list select "**Workflow state**" :
It remains to choose the workflow step to apply to the selected forms:
### Changing workflow state by email
It is possible to send an email containing a button that lets the recipient perform a workflow transition directly in Daxium-Air. The recipient does **not** need a Daxium-Air account to use it.
A common use case is to send a third party (a partner or a client) an email containing a [report](/user-documentation/build/building-the-reporting.md) generated from a submission, together with a workflow transition button. Thanks to the button, the recipient can, for example, validate or reject the report.
This is set up through the [automations](/user-documentation/build/building-forms/automations.md) feature, using either of these actions:
* **Send an email** — when you don't need to attach a Daxium-Air generated report.
* **Send a simple report** — and set the **Send report by email** toggle to **On**.
{% hint style="info" %}
The **Send a simple report** action is only available if a [report template](/user-documentation/build/building-the-reporting/report-templates.md) is associated with the form.
{% endhint %}
On both automations, a **Add a public link** section is available, with an **Add a link** button. Clicking it opens a pop-in where you configure:
* **List label** — the name of your link.
* **Transition** — the workflow transition triggered when the recipient clicks the link.
* **Validity period of the link** (in days).
* **Maximum number of clicks** on the link.
* **Messages** shown in case of success, expiration, maximum clicks reached, bad transition (when the submission is not in the initial state of your transition) and authentication request (when the user needs to be authenticated to perform the action).
## Limitation
* A single user cannot be assigned to more than **1,000 submissions.**
* A form using assignments cannot use broadcast or tasks.
* It is not possible to assign a submission to several users.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://www.center.daxium-air.com/user-documentation/build/building-forms/workflow-and-assignation.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.