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

# Attention

> The operator inbox — held calls waiting on approval, parked selections waiting on a choice, and runs that stopped and need a look.

Agents that run on their own still reach moments only a person can settle. **Attention** is where
those land: one inbox for everything waiting on you, across every agent and workflow. This page
covers the three kinds of item, why they are kept apart, and how the screen behaves when it cannot
see everything.

## Three kinds, because the next move differs

| Item                        | What is waiting                                           | What you do             |
| --------------------------- | --------------------------------------------------------- | ----------------------- |
| **Awaiting approval**       | A guardrail held an action rather than letting it run     | Approve it or refuse it |
| **Awaiting your selection** | A workflow reached a point with more than one way forward | Pick the branch         |
| **Needs attention**         | A run stopped and nobody has looked at it                 | Open it and decide      |

They are separated deliberately. Answering a held call, choosing a branch, and investigating a
stopped run are different jobs, and a single undifferentiated list would make you re-read each row to
work out which one you were being asked to do.

When you decide, you can attach a note — *why this branch*, or the values the option you chose needs.
The note travels with the decision into the run's evidence, so the reasoning is recoverable later
rather than living in someone's memory.

## Held calls come from guardrails

An **Awaiting approval** item is a guardrail doing its job. A rule with the **Hold for approval**
action pauses the matching call and puts it here rather than refusing it outright — the
human-in-the-loop posture for work that mutates something. Approving it from this screen releases the
call through the same path the guardrail held it on.

## It tells you when it cannot see everything

The inbox reads from several sources, and the screen is explicit when one of them does not answer
rather than quietly showing a shorter list:

* **"One source did not answer"** — the list is incomplete, and it names which section is affected.
* **"Can't confirm the inbox is empty"** — nothing is showing, but the screen will not claim you are
  clear when it could not read everything.
* When there is more than the screen holds, **only the oldest items are shown** — work through them
  and reload for the rest.

<Note>
  That last distinction is worth trusting. An empty inbox and an inbox that could not be read look the
  same on most screens; here they do not, so "nothing needs you" means it.
</Note>

When it is genuinely clear, it says so plainly: *no held calls, no parked selections, and no stopped
runs.*

## Next steps

<CardGroup cols={2}>
  <Card title="Approvals" href="/security-and-governance/controls/approvals">
    How an approval is requested, and what the decider is shown.
  </Card>

  <Card title="Standards & Guardrails" href="/security-and-governance/controls/standards-guardrails">
    The rules that hold an action in the first place.
  </Card>

  <Card title="Runs & evidence" href="/manage-your-agents/run/runs-evidence">
    The run behind a stopped item, and the trail your decision joins.
  </Card>

  <Card title="Orchestration" href="/manage-your-agents/run/orchestration">
    Where a workflow pauses for a selection.
  </Card>
</CardGroup>


## Related topics

- [Approvals](/security-and-governance/controls/approvals.md)
- [Orchestration](/manage-your-agents/run/orchestration.md)
- [Knowledge base](/manage-your-agents/build/knowledge-base.md)
- [How Run works](/manage-your-agents/run/how-it-works.md)
- [Onboarding](/get-started/onboarding.md)