Skip to main content
Hive prepares actions — a reply to a customer, an invoice reminder, a ticket update. In Ask (a chat with no agent picked) and Signals, the level of the account an action would use decides what happens next: on Act, where new accounts start, Hive carries the action out and tells you what it did; on Draft, it waits for a person to approve; on Read, Hive only tells you what it found. Even on Act, an action that cannot be undone, or one a safety check holds back, waits for approval, and bulk actions, saving a file to Drive and MCP server tools always ask first. A plan you ask for with Act on this on a signal comes back for your approval, even on Act. See Accounts and autonomy. On the Signals page, the Review decision panel is where you decide the actions that wait. Its promise is printed at the top: “Nothing runs until you approve it.”

Where approvals appear

There is no separate inbox for action approvals. Proposals show up where the work started:
  • Signals — a signal with a prepared action shows a review button: Review reply, Review chaser, Review nudge or Review message when Hive has drafted something, Review action otherwise, and Review actions when there are several. Approvals a signal raised appear here, and so do the cards your own agents’ runs and workflows held (below). An approval a workflow run raised before Hive began holding them also stays here until you decide it.
  • Ask Hive — an action you request in a chat that needs your approval is reviewed inline in that conversation only, and passes the same checks. It never appears in Signals. Each value on the card says where it came from — your request, a live read, Brain memory or Hive’s own wording. See Where each value came from. When Hive prepares a change again later in the same reply — a draft or email to the same people with the same subject, or a meeting with the same title and time — the repeat is withdrawn, so only one card waits. This is rolling out to workspaces gradually.
Old links to /approvals open the Signals page. Agents and workflows follow the level of the account each action runs from: on Read they take none, and on Draft each action waits on a card. On Act they carry out the actions selected for them straight away, and the audit log records each one. The exception is an action whose recipient, channel, number or link did not come from the agent’s instructions, the workflow’s own steps or words you typed in Hive — one found in an email, a public form, an app event or an AI step’s answer. Hive holds it as a card: in the Ask chat if the agent ran there, otherwise in Review decision on the Signals page of the member the run belongs to — whoever ran it, owns the schedule or owns the workflow. The card’s reason says where the destination came from. They also raise a card for the actions that always wait for a member’s click, such as a LinkedIn post, for a workflow step that changes something through a connected MCP server not set to Read, and when your own message to an agent asks it to draft or hold its actions. A public agent link takes no actions. See What agents and workflows do by themselves. To make a workflow wait for a person before any other step, add an Approval step: the run waits until a person the step names (or the workflow’s owner, if it names no one) chooses Approve or Reject on a card under Needs you in their Inbox, not in this panel. If no one decides within 7 days, the run ends as Expired.

Read the proposal

The panel is organised so you can check the exact action before you decide:
The risk word comes from the action’s blast radius: Low risk (B0), Medium risk (B1–B2) or High risk (B3–B4). See Autonomy and blast radius.
Every step of the plan, each marked “runs when you approve” or “runs automatically”. Hive attempts only the steps shown; completed actions are recorded in the Audit log and the signal is marked handled. If a card has no step Hive can carry out, it says so and Approve & run now is unavailable: choose Do not run to close it.
The plan’s summary of what it proposes, shown exactly as Hive wrote it, when the card has no single message you can edit. When the proposal sends or saves one email you can edit, the panel shows Reply that will be sent instead: that is exactly what is sent. If Hive could not read the conversation behind it, the panel says Conversation context unavailable — review the source before sending.
A reply or nudge drafted for an email signal shows, above the draft, the latest five messages of the thread it answers, oldest first. Each shows the sender’s name (or You), when it was sent and an excerpt of up to 600 characters. Email addresses are hidden.
  • For a mail signal it is the signal’s own thread. For a signal raised on a matter, it is the matter’s most recently active email thread. When the matter has more than one, the panel says The latest conversation on this matter, which has more than one — check which one the draft answers before sending.
  • When Hive may not hold every message of the thread, for example because some could not be read, the panel says so and asks you to check the source.
  • Only the member who holds the signal sees it. Owners and Admins never do, and it is not available to AI clients connected over MCP.
When no thread can be shown, the panel keeps the Conversation context unavailable note.
An approval for one of your MCP servers’ tools lists every argument the tool will receive, exactly as it is sent, under What … will be sent in this panel and on the card in Ask. Each row is labelled with the argument’s name, or a readable form of it (due_date as Due date) when that spells all of it. A text is shown whole, with its line breaks and spacing, and each tab marked ⇥; a text that would read as a number, true, false, null or JSON is shown in quotes, so you can tell it from the value itself; a number, list or nested value is shown as the JSON the server receives, one key a line, where a tab reads \t. Emoji, keycaps such as 1️⃣ and flags are shown as they are.What is sent is what the card shows: a no-break space (as Word adds) or any other unusual space is sent as a plain space, line breaks are sent plain, and a text is sent without the spaces at the ends of its lines or the spaces and blank lines around it.Hive never makes an MCP call a card could not show in full — in Ask, in Signals, or in an agent, even one that acts without a card. A call is refused instead, and Ask says what it needs, when it has:
  • more than 13 arguments, or an argument the tool does not declare (a tool whose schema declares no arguments takes none);
  • an argument name the tool does not declare other than letters, numbers, _, . and - (a name the tool declares may use letters of any script), or a name longer than 40 characters;
  • two arguments the card would name alike, such as email and Email;
  • an empty value, or a value over 20,000 characters;
  • a hidden character, such as a zero-width space or a right-to-left mark, or a text that contains ⇥, the mark the card uses for a tab;
  • an emoji joiner or variation selector outside a standard emoji (two faces joined by an invisible joiner, or a thumbs-up with a selector it is drawn the same without), an emoji or keycap written without a selector its standard form has, or a symbol with a text and an emoji form (❤ and ❤️, © and ©️) written both ways in one text. Standard emoji such as ❤️, 👩‍💻, 1️⃣ and the flag of Wales are shown and sent as they are, and so is each symbol kept to one form. An emoji newer than Hive’s Unicode data is refused until Hive is updated.
An approval prepared before this rule whose call can’t be shown in full says so here, and Approve & run now is off: choose Do not run and ask Hive again.
Why this asks first, Predicted blast radius, Rollback confidence and If you do nothing — the cost of not acting.
When more than one of your connected accounts could send the action (for example two mailboxes), choose which one. Hive sends only from your own connected accounts, with the access you have granted them now. If the account you picked is no longer connected, or is not yours, Hive refuses before approving anything, so the proposal stays open for you to pick another.
Before approving, check:
  1. the intended outcome;
  2. the exact people or records affected;
  3. any money, customer, access or reputation impact; and
  4. whether the action can be reversed.
Approving means approving the exact plan shown — target, amount, scope and wording. Check those, not just the headline.

Decide

Edit a drafted email reply

When the proposal sends or saves one email from your own Gmail or Outlook (a reply in one of your threads, a draft reply, a new message or a draft), the panel shows Reply that will be sent: the exact text that goes out. To change it:
  1. Choose Edit reply and rewrite the text. The counter shows how many characters you have used out of the limit (4,000 for an Outlook reply or draft reply, 10,000 for a Gmail reply or draft reply, 20,000 for a new email or draft).
  2. Choose Approve & send your reply to send your text instead of Hive’s. Only the text changes: the email still goes to the same people, from the same account, with the same subject, in the same thread.
  3. Or choose Discard edit to put Hive’s draft back. Nothing is sent until you approve.
When you send an edited reply, the matter it belongs to records that you edited Hive’s draft. On its next read, Signals learns from how you wrote the reply: tone, greeting, sign-off and length, never names, numbers or addresses (see Matters). If the proposal changed or expired while you were editing, Hive refuses to send it rather than sending the original draft. The same edit is on Ask’s action cards: see Ask Hive. Other proposals cannot be edited in the panel. If you want different wording or a different action, choose Do not run and ask Hive for a replacement. A denial also teaches Hive: it proposes a rule that this shape of action should not run automatically, which takes effect once it is promoted (see Learned behaviours). Approval is bound to the exact parameters you saw. If anything in the plan changes, it needs a fresh approval. An edited reply is bound to your text in the same way.

Proposals expire

A proposal waits 7 days. The panel counts down (“This request expires in …”). After that it can no longer be approved, so a stale action cannot run on out-of-date information.

Who can approve what

Only Operators and above can decide on proposals. Cards routed to a role keep its tier: when an action’s blast radius is above your role’s level, the panel says “High risk is above what your role can approve.” (with the action’s risk word) and still shows you why Hive proposed it. Cards you hold are yours to decide, at any tier. In your own Review decision panel on the Signals page, you can approve every card you hold — one raised by your own signal, run, schedule or workflow — whatever its risk: an email, a money move such as a refund, or an action that cannot be undone, such as deleting a Stripe customer. Read those cards with care: nobody more senior sees them first. A card routed to an Approver seat keeps the tier in the table. Deciding also needs an active Basic, Pro, Max or Approver seat. A member on an Approver seat decides only what is routed to them, within their role’s tier, and can ask Hive 10 questions a month about those items; see The Approver seat. While nothing is waiting for them, their Approvals page says so, and that what a colleague or one of the team’s agents sends them to approve appears there, while a workflow Approval step that names them also appears in their Inbox. Hive sends no email for either. Hive never routes an approval to a member without a seat, and withdraws the approvals waiting for a member who loses theirs. A workflow Approval step left with no approver who holds a seat fails, saying so, and Owners and Admins are told. See A member without a seat. You also need to hold the source. A proposal that came from a signal read through a member’s own connected account is listed for, and can be decided by, only a member who holds every account the signal was read from — so a member on an Approver seat, who connects no accounts, never decides one — see Who can see a signal. Another member’s proposals never appear on your Signals page, whatever your role, and neither do their agents’ or workflows’ actions. The same holds for an AI client connected through the Hive MCP server. On an account set to Act, a reply Hive wrote can still come to you as a card when it mentions an amount, a long number, a link or an email address Hive could not find in what it read. The card’s red-flag line names it. See Replies are checked against what Hive read. Role limits are one check among several. Confidence, workspace policy, spend caps and the kill switch can still require review or block an action. See Roles and permissions.

When the kill switch is on

While an Owner or Admin has engaged the kill switch, the panel says “Kill switch is on — approvals are frozen company-wide.” Nothing can be approved until someone resumes autonomy. See Safety and control.

Meeting recaps wait for the notes holder

When Hive reads a member’s Google Meet notes or transcript from their Google Drive, it raises a Meeting concluded — recap ready signal with the recap. Nothing goes to the other attendees until the member whose Drive holds the notes approves it. Only that member sees the proposal. When they approve, Hive sends the recap to each attendee as a Slack direct message, and adds an in-app card for attendees who are members without Slack. If they reject it, or no longer hold the notes account when they approve, nothing is sent. A recap is a signal, so Hive prepares one only from notes in the Drive of a member with a Max seat. See Seats and roles.

After you approve

The action runs through Hive’s executor, which holds the connector credentials — the AI model never does. The result is written to the Audit log with the full chain from signal to plan to decision to result. Reversible actions can be undone from there. A member on an Approver seat, who cannot open the audit log, undoes their own decision from its card under Just decided on their Approvals page instead. The confirmation says what actually happened:
  • On an Approver seat. The confirmation never points at the audit log, which the seat does not open: in its place it says “The receipt is kept.” and, while the decision can be undone, offers Undo.
  • Drafts in your mailbox. Approving an action that creates a draft saves it in your own Gmail or Outlook mailbox, and you send it yourself. It is never counted as sent. When you ask Hive to draft a reply to one of your email threads, the card is Gmail: draft a reply in thread or Outlook: draft a reply: approving it saves the reply as a draft in that same thread, and nothing is sent. Approving a send or an in-thread reply sends it, and the receipt keeps the provider’s confirmation.
  • A card that is no longer yours to decide. Approving or declining a card that was already decided, or that is not yours, runs nothing; Hive says the card was already decided or is no longer yours to decide.
  • No card in an answer. An answer has a card for you to approve only when the card is shown on it. When Hive tried to prepare an action in that answer and could not (it needed an answer from you, an app was not connected, or the action was refused), the answer says why in its own words. When an answer says a card is waiting but made none, Hive replaces that sentence with “No approval card was prepared in this reply.” in the language of the answer.
  • Internal notes and drafts. An internal note or a draft kept in Hive is recorded in Hive, and nothing is posted or sent. Its card reads, for example, Record an internal note, “Records a note in Hive for #finance — nothing is sent” or “Draft for Acme — not sent”. After approval it reads Recorded in Hive or Draft created in Hive, and a workspace document reads Created in Hive or Updated in Hive.
  • The kill switch mid-plan. If the kill switch is engaged while a plan runs, each remaining step reads “Stopped by the kill switch before this step ran”, and the approval reads as partly ran when an earlier step already went out.
  • A signal that comes back. When a signal returns after it cleared, an action Hive already ran for the earlier occurrence is not sent again. The result says “Already done for an earlier occurrence of this signal — Hive did not send it again. Act in the source tool if it is needed now.”
Work Hive queued for a signal — preparing a plan, an automatic action or a retry — checks the signal’s source accounts again before it plans and again right before it sends. If a source account was disconnected or re-authorised in the meantime, or the member who asked no longer holds it, Hive stops: nothing is sent, and the signal leaves your feed. If the situation still holds a day later and the access is back, Hive raises it again.

Autonomy and blast radius

When Hive may act without asking.

Audit log

Receipts and undo.

Triage signals

Act on, snooze or dismiss signals.

Safety and control

Kill switch, policy and spend caps.