> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/workflow/branching-and-approvals.md).

# Branching & approvals

### Workflow Branches 

Branches let a single workflow split into different paths based on conditions about the request, the requester, time, or context. Use them to build multiple scenarios in one workflow (for example, handle HR vs. IT, US vs. EU, inside vs. outside office hours) without duplicating workflows.

#### What to expect

* One trigger, many outcomes: evaluate conditions and run different action sequences under each branch.
* Independent evaluation: each branch runs only if its condition is true. Multiple branches can run if several conditions match; make conditions mutually exclusive if you want only one path to fire.
* Mid‑flow decisions: insert a Branch anywhere in your action list to fork later steps based on updated fields or tags set earlier in the same workflow.
* Full audit: which branch(es) ran is logged in the request timeline.

#### What you can branch on

* Request fields: service, status, priority, inbox, tags, channel, source, SLA state, snooze/waiting, etc.
* Requester attributes: department, team, location, manager, contract type, seniority, employment status.
* Time and context: Office hours (within/outside), created date/time, day of week.
* Custom signals: your own tags or fields added earlier in the flow, or responses from webhooks.

#### Typical use cases

* Language routing: if language = fr → reply with French template; if = en → English template.
* Access requests: if service = App Access and office = Madrid → set approver = local manager; else → app owner.
* After‑hours handling: if outside office hours and priority < P1 → auto‑reply and queue; if outside hours and P1 → notify on‑call.
* Region/team triage: if requester.department = Sales (EMEA) → HR‑EMEA inbox; if = Sales (AMER) → HR‑AMER inbox.
* Risk paths: if tag = “incident” → set priority High, add security followers; if tag = “FAQ” → auto‑reply and close when acknowledged.

***

## Approval requests

#### What is an approval request, and why is it important?

In a corporate environment, certain actions — such as accessing an app, ordering new hardware, or requesting time off — often require **prior validation**. This validation ensures that the right people are aware of the request, confirm its legitimacy, and approve it before resources are allocated or changes are made.

Approvals help businesses:

* Maintain control over costs and security
* Ensure alignment with internal policies
* Improve accountability across teams

Siit includes a powerful and flexible **Approval Request** feature that fits seamlessly into your automated workflows. Whether it’s granting app access, ordering equipment, or processing a specific employee request, Siit enables you to trigger **automated approvals** to the right people — at the right time.

#### How to set up an approval in your workflow?

The **Approval** is an action that can be added to any requests workflow via the "Select approver" action.

{% stepper %}
{% step %}

### Add an Approval action

Add an **Approval** action at the point where validation is needed.

![](/files/e495b31b16697b35da816a3c24ccb939f2b83bd6)

Once added, it will automatically present the two branches for the "approved" or the "rejected" option, allowing you to configure follow-up actions according to the choice made.

![](/files/ba0967e5743aff7a21d49a368c338487466e5dea)

You can set up **single** or **multi-level** approval sequences.
{% endstep %}

{% step %}

### Define the approver

* Use dynamic fields like “Manager” or “App Owner” to automatically pull the right person from your data.
* Or assign a fixed employee as approver.
* Pick a team or an inbox instead of a named person. Everyone in the group is notified, and the first to respond decides for the group.

  <figure><img src="/files/bJWDqseqDy2tQmyImYmd" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Set up reminders

Set up **reminders** to ensure follow-up if no action is taken. If the approval is not given after a certain time (from 1 day to several weeks), you can configure automatic reminders directly from the approval configuration to prevent the rest of the flow from proceeding.

![](/files/b387a60c2542ea3bb875918eb9f1824d2ac67c73)
{% endstep %}
{% endstepper %}

#### How to approve?

Approvers will receive a notification on Slack or Teams. They simply review the request and either Accept 👍 or Reject ❌.

![](/files/3030e620672f9d7cb006d9f451840b8a2f58d3cb)