---
title: Inbox
description: Review and act on human-in-the-loop tasks — approve, reject, reassign, or modify paused workflow steps.
---

The Inbox is where workflows come to you for a human decision. When a flow reaches a **Human** node, it pauses and creates a task in the Inbox. Nothing in that flow continues until someone takes an action.

The header badge shows live counts: **open**, **approved**, and **rejected** tasks.

## Sections

The Inbox has three sections in the section rail:

### Tasks

The Tasks section lists all human-in-the-loop decision requests. Use the status pills at the top to filter by `open`, `all`, `approved`, or `rejected`. Use the search box to find tasks by prompt text, task ID, or tag.

**Task card**
Each task shows:
- The task prompt or description.
- The flow and node that generated it.
- The time the task was created and any configured timeout.
- A **notes** field — type a note before approving or rejecting; it is recorded in the audit ledger.

**Actions**
- **Approve** — allows the flow to continue.
- **Reject** — marks the task as rejected; the flow routes to the rejection path (if configured) or stops.
- **Reassign** — reassign the task to another user or role.
- **Modify** — propose a modification to the task's payload (for tasks that accept a structured response).

Navigate between tasks with keyboard shortcuts `j` (down) and `k` (up).

### Escalations

The Escalations section shows tasks that have timed out and been escalated to a different approver or role. Each escalation card shows the original task, who it was escalated to, and the reason.

### Approvals

The Approvals section shows a chronological view of all completed approvals (approved and rejected) for this session. Use this to confirm that actions you took were recorded correctly before closing the browser.

## Configuring Human nodes

Human nodes in a flow are configured in the **flow editor Inspector panel** when the Human node is selected. Key settings:
- **Approvers** — who should receive this task (by user, role, email, or capability).
- **Quorum** — how many approvals are required.
- **Escalate on timeout** — whether to escalate to a fallback approver after a timeout.

See [Workflows](/docs/using-the-app/flows) for details on the Human node inspector.

## Related screens

| Need | Go to |
|---|---|
| Flow design | [Workflows](/docs/using-the-app/flows) |
| Process approvals | [Processes](/docs/using-the-app/pipelines) |
| Access policy | [Access](/docs/using-the-app/governance) |
| Run history | [Activity](/docs/using-the-app/runs-and-observability) |