Help Center

Docs

The Approvals Queue

Review, approve, and reject the actions your AI Agents propose before they touch your CRM.

What the queue is

One place to clear every pending action across all your agents.

An action lands in the queue when it needs a person: because the level the agent runs at holds it, because the permission on that action is Ask first, or because it is on the always-asks floor that no level moves. Looking things up never waits for you. The queue’s home is the Inbox section of the Agents home, and a pending count rides the Agents item in the sidebar so you know when something is waiting.

Nothing in the queue has happened yet. Each item is a proposed change held back until someone decides.

What each card shows

Enough to decide without leaving the queue.

  • What: which agent wants to do what, to which record, in plain language.
  • The change: one line with what would be sent or changed. A draft reads To Dana Lee: Pricing follow-up, a field change reads Stage: Negotiation (was Proposal), and a merge reads Acme Inc into Acme.
  • What approving does: one sentence. Above the low tier the risk opens it, as in High risk., instead of sitting in a badge.
  • Decide by: the agent’s name and the deadline, in your own time zone: Decide by Thu 2:00 PM. If nobody does, it's skipped. In its last two hours the deadline turns to the warning colour.

Open a card for the rest: the whole draft, word for word, every value the action would use, a link to the record, and one line on why the agent is asking, which starts Why: and gives what started the run and the agent’s purpose.

Approving and rejecting

On the card, in the open card, or from the keyboard.

Approve and Reject sit on the card itself, so clearing a queue does not mean opening one card per item, and the open card carries them again at its foot. From the keyboard, j and k move between cards, Enter opens one, x selects it, 1 approves and 2 rejects.

1

Review the proposal

Read what would be sent or changed and when it has to be decided by. Open the card for the whole draft, every value and why the agent is asking.
2

Approve

The decision is saved at once and the card reads Queued while the change is carried out in the background. Once it has been made, it reads Done.
3

Reject

The action is discarded and never runs. In the open card you can add a reject note first. It is optional, and it belongs to that action alone.

A note is kept per action. A note typed in one card never follows you to another card, and rejecting from the list or the keyboard sends that action’s own note, or none.

Approval does not run inside the web request. It queues the exact change you read. Double-clicks, another tab, retries, and worker restarts return the same decision instead of duplicating the change.

Filtering the queue

Find the items you care about in a busy queue.

Filter by agent to focus on one, by record type to focus on companies or deals, by risk to triage high-risk items first, and by state: Waiting on you, Approved or Rejected. A filter that matches nothing says which filters are narrowing it. Arriving from a run shows Filtered to one run, which you can clear.

A proposal becomes stale if its run ends or the original grant, record, recipient, values, or authority no longer matches. It must be proposed again before it can run.

Deciding several at once

Tick the cards, then decide them together.

Tick the cards you want, up to 100 at a time, and a bar offers Approve with the count and Reject. Each asks you to confirm first. Approving says that each action makes its change for real and cannot be undone from the queue. Rejecting has its own optional field, Note for these rejections, and a note typed in any one card never rides along.

A bulk decision covers only the cards you ticked, never everything the filter matches. Each action is still decided on its own, and if they do not all end the same way, the list refreshes to show where each one stands.

Decided actions

Decisions stay visible after a reload.

A decided card stays where it is and says what happened to it. To look back, set the state filter to Approved or Rejected: each shows the most recent decisions of the last 30 days, and they are still there after a reload. A decided card is a record, with nothing to tick, press or note.

  • Approved holds everything someone approved, whatever became of it: Done, Queued, a line saying it couldn’t run and why, or Expired before it could run.
  • Rejected holds what did not run on a decision: Rejected, and Expired, not run for an action nobody decided in time.

Who decides

Admins by default, and everyone else is told where they stand.

Deciding needs the permission to approve agent actions, which admins hold by default. For everyone else the Agents home opens on Agents instead of the Inbox, and the Inbox shows this in place of the whole queue: You need permission to approve agent actions before you can decide this one. An administrator in your workspace can grant it. A run’s Needs you section works differently: it still lists each action and its deadline, and shows the same sentence only where Approve and Reject would be.

The one person told about a proposal is the agent’s creator. When an agent you created proposes something, you are told in your notifications and in My Work, and again before it runs out of time. Nobody else is notified: the proposal waits in the Inbox, where anyone who can approve, an admin by default, can decide it. If your role cannot approve, ask one of them to decide it, or to give you the permission.