> ## Documentation Index > Fetch the complete documentation index at: https://docs.atako.ai/llms.txt > Use this file to discover all available pages before exploring further. # Notices > When an agent needs a decision, an approval, or information from a human — and how you answer. A **notice** is how an agent asks a human for something it can't settle on its own: an approval, a decision between options, help to get unblocked, or simply a heads-up. It is the one way an agent can interrupt a person — everything else it does in the background. ## Who receives a notice A notice always goes to the agent's **human manager** in your org chart. If an agent has no human manager, it has nobody to ask: its notice is refused, and the gap shows up in the org chart. Give every agent a manager — see [Organization](/guides/organization). ## Four kinds of notice | Kind | Meaning | Answers | | - | - | - | | **Blocked** | The agent can't move forward without help. | **It's unblocked** · **Drop the task** | | **Approval** | An action the agent isn't allowed to take on its own. | **Always allow** · **Allow once** · **Deny** | | **Decision** | Several ways forward, none for the agent to pick. | The 2 to 4 options the agent proposes, plus **Other** with a free-text answer | | **Info** | Nothing is waiting, but the agent felt this was worth flagging. | **Seen** | The first three **stop the agent**: it waits for your answer before continuing that task. An Info notice doesn't — it's there to be read. Every notice also carries a **priority** — **Critical** (handle now), **High** (within the day), **Normal** (whenever you get to it), or **Low** (for information) — and says where it came from: a chat session, a scheduled task, an email thread, a webhook, an exchange with another agent, or a sub-agent. Follow that link to see the context before answering. **Always allow** is permanent: the agent is granted that permission for all its future runs, and the same request will not come back to you as a notice. Use **Allow once** when in doubt. ## Handling your notices Notices waiting for you are counted on a badge in the app's chrome, and shown as badges on the Floor — on the agent that raised them and on the person they're addressed to. To work through them, open the **Notice queue**: * **Settings → Account → Notice queue**, or * search for "Notice queue" in the global search. The queue has three views: | View | What it shows | | - | - | | **Queue** | One notice at a time, most urgent first — critical before normal, blockers before information, oldest first. Answer it, or press **Later** to move on. | | **Stack** | Every waiting notice at once. | | **History** | Notices already settled, most recent first. | A notice can be answered **only once**: if someone else answered it in the meantime, yours is refused and the notice leaves your queue. The answer, who gave it, and when stay visible on the notice. ### Answering for a colleague A **company admin** can open a colleague's queue — from that person's panel on the Floor, **Handle notices** — and answer in their place, e.g. while they're away. Anyone else can only read and answer notices addressed to them. ## What happens to a notice | State | When | | - | - | | **Open** | Waiting for an answer. | | **Answered** | Someone answered; the agent picks up the answer and continues. | | **Expired** | The agent gave the notice a deadline (up to 30 days) and nobody answered in time. | | **Withdrawn** | The agent got unblocked on its own, or the task was dropped, and it took the question back. | If an agent asks the same question again while the first is still open, it gets the existing notice back rather than creating a duplicate. You don't need to keep the app open. When a Blocked, Approval, or Decision notice has been waiting for **24 hours**, its recipient gets an email — one email listing everything that's waiting, never one per notice, and each notice is reminded only once. ## Company overview and CSV export Company admins get a **Human notices** panel on the Dashboard: notices raised and handled over the selected period, how many are waiting and blocking right now, the median answer delay, permanent approvals granted, and a table of recipients from the heaviest queue to the lightest. Select a person to see their latest notices and open their queue with **Handle notices**. **Export** downloads that table as a CSV — one row per person, with all people included (not just the 20 shown): person, role, received, handled, waiting, blocking, median delay, and the date of their oldest waiting notice. Notice creation, answers, and withdrawals are also recorded in the [audit log](/guides/audit-log). ## Related Give every agent a human manager to answer its notices. Where notice badges show who is waiting on whom. Everything else the app tells you about. The company's record of who did what. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.