> ## Documentation Index
> Fetch the complete documentation index at: https://collabase.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Collabase documentation. Interface labels are quoted in English, as they appear in the product.
> Features marked Enterprise need the Collabase Enterprise Edition licence.

# Flow approvals

> Two kinds of approval: a second admin who must agree before a flow in a sensitive workspace goes live, and people who approve a step while a flow runs.

Collabase has two approvals that work independently. One guards the **publication** of a flow. The other pauses a **run** until a person has decided.

## Approve a publication

In a **Sensitive** workspace, a flow can do harm if it is wrong, so publishing it or switching it on needs a second person. Switch on **Sensitive** under **Settings** of the workspace.

**1. Ask for approval**

The editor selects **Ask for approval** instead of **Publish**. A banner shows that a request is pending. The version that was live stays live while the request waits.

**2. Admins are told**

The other admins of the workspace get a notification with a link to the request.

**3. Decide**

An admin opens the request, looks at the flow and approves or rejects it. The decision must come from an admin who did not ask for it and did not make the last change to the draft.

**4. Result**

An approval publishes the flow or switches it on, as the admin who approved. A rejection changes nothing. The editor is told either way.

The editor can withdraw a pending request. If anyone changes the draft after the request, the request is withdrawn on its own, so nobody approves something they did not see. The audit trail records the request and the decision.

## Approve a step in a run

Add **Ask for approval** from the flow control plug where a person must decide before the flow goes on, for example before an order is released.

| Input | Description |
| - | - |
| **Approvers** | The people and groups who may decide. They do not have to be members of the workspace. |
| **Text for the approver** | What the approver reads. |
| **Give up after (days)** | How long the run waits. The default is 30 days. |

Each named person gets an inbox entry with a link. The page shows the names of the flow and the step, your text and the deadline, and nothing else of the run. The first decision counts. The step returns the decision, so a later step can read it. If nobody decides in time, the run ends as **Timed out**.

While it waits, the run is **Paused** and holds no resources.

## Approve a tool of an agent

An [AI agent](https://collabase.ch/docs/automation/agent-step.md) can ask a person before it uses a tool. The approvers see the tool and the exact input, and only that input runs after they approve.

## Related

* [Workspaces](https://collabase.ch/docs/automation/workspaces.md)
* [Runs and approvals](https://collabase.ch/docs/automation/runs.md)
* [Agent tools](https://collabase.ch/docs/automation/agent-tools.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.