# Add new
Company-wide confirmation flows are created and maintained in **Settings → Confirmation flows.** Once You set up a flow, it's ready for Your team to use on new invoices and purchase orders. Only Administrators can create and edit flows.
### Creating a new confirmation flow
{% stepper %}
{% step %}
### **Open the confirmation flow details page**
1. Go to **Settings → Confirmation flows**.
2. Click **Add new** (or click an existing flow to edit it).\
→ You are taken to the **Confirmation flow details** page.
{% endstep %}
{% step %}
### **Fill in the general information**
On top of the page, define the basic properties of the flow.\
**Flow name (required)**
* Can contain any printable UTF‑8 characters.
* Minimum **1** character, maximum **128** characters.
* Must be **unique** in your company (no two flows with the same name, case-insensitive).
* If a name already exists, saving fails
{% hint style="info" %}
Good practice: use a name that tells people what the flow is for. Examples:
* “Marketing invoices < 5,000 EUR”
* “Capex > 50,000 – CFO approval”
* “PO – IT purchases – Dynamic”
{% endhint %}
### **Description (optional)**
* Can contain any printable UTF‑8 characters.
* Up to **256** characters.
* Example: “Use for office cost invoices up to 1,000 EUR”
{% endstep %}
{% step %}
### **Dynamic (Static vs Dynamic flow)**
**When you need it?**
You need a Dynamic flow when You have a standard approval chain, but not every invoice needs every person. Instead of creating separate flows for "under 500 EUR", "under 5,000 EUR", "over 50,000 EUR", a Dynamic flow lets You keep one shared flow structure and automatically adjusts based on invoice amount. [Read more.](/fitek-learning-space/latvian-latviesu/purchase-invoices/apstiprinasanas-darbplusmas/dynamic-flow.md)
{% endstep %}
{% endstepper %}
* **OFF → Static confirmation flow**: all steps and approvers stay the same, regardless of invoice amount.
* **ON → Dynamic confirmation flow**: the system automatically removes approvers whose monetary limit is higher than the invoice total (except users in the last step).
Default: **OFF** (Static).
***
For detailed information about each type, see:
***
**Step 3 — Build the steps and approvers**
A confirmation flow consists of **steps**, and each step has one or more **approvers**. Start simple – you can always adjust it later.
**Add the first step**
* Click **Add the first approver**.
* A dropdown opens with eligible users:
* Active in the current company
* Membership not expired
* Have **Approver** or **Administrator** role
* Not already used in this flow
* Click the user you want → **Step 1** is created.
**Add next steps**
* Click **Add next approver** for Step 2, Step 3, and so on.
**Rules:**
* Steps are always ordered from **1 to n**.
* You can have up to **20** steps in one flow.
* If you click the “X” or click outside the dropdown before choosing a user, the blank step is discarded.
**Delete a whole step**
* Click the **trash/delete** icon on the right of the step and confirm when prompted.
**Add parallel approvers (same step)**
If you want several people to review at the same time, click **Add parallel approver** (plus icon) in an existing step.
**Rules:**
* You can have up to **12** parallel approvers in one step.
For detailed configuration options (Parallel vs “X of Y”), see:
* [Parallel and X of Y approvals](https://fitekglobal.atlassian.net/wiki/spaces/FUG/overview#)
***
**Step 4 — Set the last step**
The last step must have at least one user with a role that can **complete workflows** (for example, **Approver + Completing workflow**, **Approver + Assigner + Completing workflow**, or **Administrator**).
***
**Step 5 — Save the confirmation flow**
Click **Save**. Fitek checks:
**Unique name**
* No other flow in the company has the same name (case-insensitive).
**Last step roles**
* All approvers in the last step have allowed roles that can complete workflows.
* If not, they are highlighted and saving is blocked.
**Name length**
* Flow name is within **1–128** characters.
If all checks pass, the flow is saved. Fix any highlighted fields and try again if needed.
***
**Step 6 — Delete a confirmation flow**
You can only delete flows that are **not used in automation rules**.
* If a flow is in use, the **Delete** option is greyed out and shows a tooltip.
* To delete an **unused** flow, click the **delete** icon at the top-right of the flow block, then confirm.
> **Best practices**
>
> * **Keep the first version simple.** Start with a few clear steps and approvers. Refine it later based on how your team uses it.
> * **Use Dynamic flows when you have clear monetary limits.** They automatically shorten approval chains for small invoices.
> * **Name flows clearly.** Your team should understand which flow to use just by reading the name.
> * **Test before activating.** Keep **Active = OFF** while building and testing, then turn it **ON** when ready.
---
# 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://fitek-learning.fitek.com/fitek-learning-space/latvian-latviesu/purchase-invoices/apstiprinasanas-darbplusmas/add-new.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.