Skip to main content
The Attention tab on the Signals page is where your team works through what Hive has caught. Every choice you make here does two things: it handles the signal in front of you, and it teaches Hive what to raise next time.
Acting on, snoozing and dismissing signals needs the Operator role or higher, and an active seat. See Roles and permissions.The feed shows only the signals you hold: the ones read from your own connected accounts, or raised on your own matters. That holds for every role — an Owner or Admin never sees another member’s signals or decisions here. See Who can see a signal.

Find what needs you

Open Signals from the sidebar. The Attention tab has one filter bar. From left to right: Each choice shows how many signals it would give you. A count always applies every other filter you have on, but never its own: under Needs you, the Severity counts add up to the Needs you count, and that is the number of rows the list shows. Counts reflect everything that matches, not just the loaded rows. The feed loads 50 rows at a time, already in the order you sorted by, so the signals with the most at stake are on the first 50 rows rather than waiting on a later page; use Load more for the rest. Chase signals are not in the feed. A Chase or an Invoice to chase is follow-up work Hive prepares on one of your matters, not something new that needs you, so the Attention feed leaves those signals out, and so does every count on the bar and the Value across open signals number above it. A chase that waits for your approval still shows here, as its Review chaser row under Needs you, because that row is where you approve it. You also find chases on the matter, where each requirement shows its chases and a chase waiting for you shows as Draft waiting for your approval, and here, by picking Chase or Invoice to chase under Type, which shows them with their counts.

The three states

Stage shows each signal in one of three states. Each state gathers one or more of the stages a row is labelled with (see Stages): An older link that names Action needed opens Needs you, and one that names Updates opens Hive is on it.

The Done view

Choose Done under Stage to see every signal closed in the last 7 days. Each row says who closed it and why, for example You marked this Not for me, A teammate approved Hive’s action or Hive closed this · it looks done; a teammate is never named (see See who closed a signal). A closed row reads Done where it used to read Handled or Dismissed. Open a row’s details to see until when you can reopen it, and Reopen beside that (see Reopen a closed signal). After 7 days a signal leaves Done. Done shows only your own signals, like the rest of the feed, and its count is not part of All open or of the Value across open signals number. Under the bar, each active filter shows as a chip. Select a chip’s × to drop that filter, or Clear all to drop them all and the search. On a phone the search box, a Filters (n) button and the Stage control stay at the top of the screen as you scroll. The Stage control shows its four stages two by two, so none is hidden off the edge of the screen. Filters (n) opens a sheet with Severity, Type, Account, Matter and Sort; the number counts the filters you have on. On a phone each signal is one row: its severity, what happened on up to two lines, and one grey line with the severity, the review label, the source, how long ago Hive raised it and its matter. Tap a row with proposed actions to open its review; tap any other row to open Signal details from the bottom of the screen, with the evidence and the row’s actions such as Act on this, Snooze and Dismiss. The summary chips above the tabs wrap onto a second line rather than scroll sideways. Your filters, the sort and the selected signal are part of the page address, so you can copy the link to send a teammate exactly the view you are looking at. They still need the right role and department access to open it. Each row shows where the signal came from, how long ago Hive raised it, the matter it is on and its severity. When Hive can’t confirm some of the signals listed, a single note above the list says how many, and those rows are marked Unconfirmed. See How Hive closes a signal on its own. Open Details on a row to see the evidence, readings and source link. Rows that carry proposed actions show Review actions (for a single proposal, Review action, or a label naming the draft, such as Review message), which opens the review panel described in Review and approve. There you can edit a drafted email reply before you approve it. A row whose proposal has no step Hive can carry out says so instead of offering it for approval: open it and choose Do not run to close it. Both the details and the review panel have Open in Ask. It opens Ask with the signal, and its matter, written into the message box, with a From signal chip that tells Hive which signal the chat is about. Nothing is sent until you add your question and send it. See Open a signal in Ask.

When the feed is empty

An empty feed tells you why it is empty:

Act on a signal

Choose Act on this to ask Hive to work the signal: Hive prepares a plan and comes back to you with it. It is offered on signals that are new, that Hive is only watching, or that Hive could not queue for preparation.
1

Choose Act on this

The row changes to Asking Hive… and then “Preparing a response”. Your request has been accepted; it has not run yet.
2

Review the plan

When the plan is ready the signal returns to Needs you with Review action. Nothing external happens until you approve it, even when the account it would use is on Act. If the account is on Read, there is nothing to approve: Hive only tells you what it found.
3

If preparation fails

Each preparation keeps time for writing the plan: when reading your tools, or a short wait for a busy AI provider, runs long, Hive stops and plans from what it has already read. When the plan it writes is not valid, Hive gets one more try to correct it before the preparation counts as failed. The signal stays in your feed as “Preparing a response”, and what the preparation used comes back: the prepared action returns to your seat’s month, or the credits to the pool. Hive retries a failed preparation automatically, up to three times over about 45 minutes, for example after an AI provider error. If it still cannot, Hive’s team is alerted and handles the failed preparation; Hive does not yet try it again by itself. There is nothing for you to retry. If Hive could not even queue the work, it queues it again by itself, and you can choose Act on this meanwhile. When the AI provider says it is too busy and names a time to come back, Hive waits until then before it tries again, even when that is a few hours away, and the signal stays as “Preparing a response” meanwhile. Waiting for a busy provider does not count as one of the three retries.
4

If Hive stops working on it

Once the retries are used up, or a preparation has gone seven hours without finishing, the signal no longer says “Preparing a response”. It shows as an ordinary signal with “No suggested action yet.”, with no Act on this and nothing to retry. You can still open its details, or dismiss it. The signal itself is kept as it was.
Hive refuses Act on this while the kill switch is on, while it is already working the signal, and on signals that are already closed. If Hive is updated or restarted while it prepares a signal, it picks the preparation up again by itself once the update is live, and carries on as it would have. If the work was lost for longer, Hive picks it up about ten minutes later: a preparation picked up that way always waits for your approval, even when the account it would use is on Act, and if it is interrupted again, Hive’s team handles it, as for any failed preparation. On Business, preparing a signal uses AI credits at what it costs Hive: when Hive starts it, the credits of the member whose account raised the signal; when you choose Act on this, your own. When those credits, and any extra usage allowed, are used up, Hive prepares nothing more automatically, and new signals arrive as needs reply, with no draft. On an earlier plan, preparing a signal counts as one of your Max seat’s prepared actions for the month (25 on Starter, 120 on Team), whether Hive starts it or you choose Act on this. Within that fair use it is included in your seat and never draws on your workspace’s credit pool. Above it, a preparation uses about 11 credits from the pool (a client reply about 12). When the pool is empty or your limit for Signals above fair use is reached, Hive prepares nothing more automatically: new signals arrive as needs reply, with no draft. You can still choose Act on this on one: above fair use it uses credits from the pool, and while the pool is empty Hive cannot prepare it. If a preparation that was already paid for could not start, whether Hive started it or you chose Act on this, preparing it again uses what was already paid: it is not charged again or counted as another prepared action, even in a later month or after Hive has seen the same situation again, so an empty pool does not stop it. A preparation that fails on Hive’s side is not paid for at all: its prepared action or credits come back. See Fair use and credits. In a workspace’s first 14 days, Hive prepares at most 10 high-risk proposals (an email, a write to a connected tool, a payment or an access change: tier B3 or B4) for each member a day by itself, so a new mailbox’s backlog does not arrive as dozens of cards at once. Once a member has had 10 that day (midnight to midnight, UK time), Hive prepares nothing more for them automatically until the next day: new signals still appear, marked Plan delayed with “No response is prepared yet.”, and you can choose Act on this on any of them to have Hive prepare it now. Your own Act on this is never limited. Hive tries again by itself the next time it sees the signal. Act on this needs a Max seat. A member on a Pro seat is not offered it, and Hive never prepares a signal for them; a member without a seat, or whose seat is suspended over the plan’s limit, cannot use the workspace at all. When a member’s Max seat changes to a Pro seat, or they lose their seat, the proposals and prepared drafts waiting for them are withdrawn. Hive prepares the signal on your workspace’s Efficient background model. If it prepares the same signal again, it uses the model it used the first time, as long as your workspace still allows that model. See Signals preparation.

When Hive looks things up first

Hive prepares every signal on its newer agent runtime, so it can look things up before it proposes anything:
  • A signal that came from one member’s connected account or chat is prepared with what that member can read: their documents, the Business Brain, their signals, emails waiting on their reply and their own connected apps. That includes their own MCP servers, but only the reads that may run with nobody there: a tool Hive reviewed as a read on a server marked Direct reads, or a tool Hive has classified read-only — never a paid read or one that searches the web. Admins get no wider reach here than in their own chats.
  • A mail signal (someone is waiting on a reply, or a thread went quiet) is prepared by reading the whole thread from that member’s own mailbox. If a reply is owed, Hive writes it in context and in the member’s own tone, and prepares it as a reply in the same thread, never a canned holding note. The mailbox’s Read, Draft or Act level then decides whether Hive informs, leaves a card to approve, or sends it. A reply goes to the latest person on the other side of the thread; when only the member has written in it (a follow-up, or a first chase), it goes in that same thread, from the account that holds it, to the person the member wrote to. Hive never prepares a reply in a thread the member was only copied on (on Cc or Bcc, or through a group or forwarding address), whichever signal it is preparing. A mail signal is never prepared as only an internal note: Hive either prepares the reply, or closes the signal with the reason no reply is owed.
  • Any other signal, such as one from workspace-wide data, is prepared from the signal itself and your company profile only. Hive reads nothing of any member’s.
Hive never searches the web while it prepares a signal. Each preparation is also kept short: it makes at most 12 lookups, and once it is close to its time limit it stops looking things up and writes the plan from what it has already read, saying what it could not check. A slow connected app no longer holds a signal at “Preparing a response”. Whatever it proposes goes through the same checks as before: the actions your workspace allows, the recipient checks, approvals, the autonomy your workspace has granted, and the kill switch. Then the level of the account the action would use decides what happens to it — see Read, Draft or Act:
  • Read — the signal tells you what happened so you can take a look. Nothing is proposed or done.
  • Draft — the response waits for your approval.
  • Act — Hive takes the action within your limits, and the signal says what it found and what it did. An action that cannot be undone, or one a safety check holds back, comes to you as a card instead. A plan you ask for with Act on this always waits for your approval.
If you have more than one account for the app, for example two Gmail mailboxes, Hive uses the one on Act when there is exactly one. Otherwise the approval shows a Send from picker listing your accounts on Act, or on Draft when none is on Act. The picker starts on the account the signal came from, such as the mailbox the email arrived in. Nothing runs until you pick an account and approve. Action cards in Ask show the same picker. See Which account an action uses. Every response Hive prepares is recorded with what was decided and why, whether it was carried out, approved, declined, refused by a safety check or only held back to watch. See Autonomy and blast radius. Hive moved every workspace to this runtime on 3 October 2026. A card Hive prepared before then can’t be carried out: if you approve one, nothing is sent, Hive says so, and the signal leaves your feed. If the situation still holds, Hive raises it again later and prepares it afresh. Declining an older card works as usual. If Hive finds nothing needs doing, for example because the invoice was already paid or the email was only a meeting invitation, the signal closes as No action needed and its row gives Hive’s reason. It is not a failed preparation, so Hive does not retry it. Hive prepares it again if the signal comes back stronger. The same happens when every action Hive proposed was refused by its safety checks — for example a reply to an address that is not in your recipient directory: there is nothing you could approve, so Hive closes the signal as No action needed instead of showing an approval card with no steps. When a preparation would propose nothing, Hive works out why before it ends, so these usually close as No action needed with a reason. If it still can’t settle on one, the preparation fails: Hive retries it automatically, and then its team re-runs it.

Snooze: decide later

Snooze a signal when it is real but not for now. Choose Snooze and pick:
  • For an hour
  • Until tomorrow (24 hours)
  • For 3 days
  • For a week
A snooze is always between 5 minutes and 30 days. It lapses on its own and the signal comes back to the feed. It also ends early if the signal’s severity rises above the level it was snoozed at, or if work on it starts. To bring a snoozed signal back straight away, choose Wake now. You cannot snooze a signal Hive is actively working.

Remind me

Choose Remind me when you want a signal out of the way until a time you pick, and a nudge when it arrives. The menu reads Remind me — only you, in your Inbox. Pick Tomorrow 9:00, Next Monday 9:00, or any date and time from 5 minutes to 30 days ahead, then Set reminder. A time outside that window is refused, not moved.
  • The signal is snoozed until then, and its row reads Reminder set for the date you chose.
  • When the time comes, only you get a reminder: a personal Inbox card titled Reminder: <signal>. It never notifies anyone else or Slack.
  • Setting a new date replaces your earlier reminder on that signal.
  • The reminder is cancelled if the signal resolves, is dismissed or is withdrawn, or if you choose Wake now. It is not sent if you no longer own the signal or are no longer an Operator or above.
  • On a matter, the reminder appears on the matter’s timeline.
Remind me is not offered on a signal Hive is working on or one that is dismissed. An AI client can set one with the signals_remind tool of the Hive MCP server.

Mark a notification useful

When Hive notified you about a signal, its Details offer Useful next to Dismiss. When Hive has prepared an action for it, Useful is in the review panel instead. Select it when the notification was worth getting: Hive then notifies you about more medium-severity signals like it. The button stays highlighted while your mark stands, and a row with Details also shows Marked useful. Select Useful again to take the mark back. Your marks count only for you, and only marks you give yourself count. See How Hive learns what to notify you about.

Dismiss: say why

Choose Dismiss when a signal is not useful. Hive asks Why are you dismissing this? and offers four answers. Every dismissal needs one: there is no way to dismiss without saying why, because the answer is what changes what Hive raises next. The confirmation always states what actually happened. If Hive could not learn anything from a dismissal, the toast says so.
For mail signals, “stay quiet about this record” means this conversation thread, not every thread with that person.

Stop a sender or a company

On an Awaiting reply or Went quiet email signal, Not for me asks Stop hearing from them? and offers:
  • Just this one — dismisses this signal only.
  • Stop for the person — no new email signals from that person’s address for 14 days.
  • Stop for everyone at their company domain, such as acme.com — no new email signals from anyone at that domain for 14 days. Public email domains such as gmail.com, outlook.com, hotmail.com, icloud.com and yahoo.com (and the big regional providers such as gmx.de, orange.fr, libero.it or qq.com) are never offered, because everyone at them is not one company. Your own company’s domain — the domain of the mailbox the signal came from — is never offered either, so stopping a colleague never quiets your whole team. Only the exact domain is stopped, not its subdomains.
The stop is always for the person the signal names. If someone else has written in the thread since the signal was raised, Hive does not offer a stop on it — dismissing still works as Just this one. A sender stop applies only to your own mailbox: a teammate’s email signals from the same person keep notifying them. Hive works out the address from the email thread itself; it is never shown on the signal. The stop is listed under Muted types, where you can lift it (see Manage muted types). AI clients connected to Hive over MCP never see your sender stops, because they name an address from your mailbox.

Whose signals a dismissal quiets

A dismissal that stays quiet about a record (Done it or Already done) quiets it only for the connected account the signal came from. A teammate’s matching signal from their own account keeps notifying them. Signals from workspace-level sources that are not tied to anyone’s account are quieted for the whole workspace, as before. Some signals are handled differently:
  • Mail and files. A mail thread is never quieted by another member’s dismissal. Not for me or Wrong on a mail thread counts toward alert fatigue within that one mailbox (see below).
  • Cross-tool signals. Dismissing a cross-tool signal keeps it quiet on later passes for the person who dismissed it.
  • When nothing can be learned. If Hive cannot tie the signal’s source to one of your own connected accounts, or the signal spans more than 8 accounts, the dismissal closes the signal but changes nothing about future detection, and the confirmation says so. The signal may come back.

How dismissals reduce noise over time

Dismissals marked Not for me or Wrong feed Hive’s alert-fatigue gate. When at least five signals of one type have been surfaced in the last 14 days and 80% or more of them were dismissed, Hive stops notifying about that type. This lifts automatically as those dismissals age past 14 days, so a type muted by feedback can come back if the situation changes. Votes are counted per kind and per connected account:
  • Only the account it came from. Your vote quiets only findings of the same kind from the same connected account. One person’s votes never silence alerts on someone else’s accounts, or on your other accounts.
  • Mail threads learn as a family. In your mailbox, Awaiting reply and Went quiet threads learn together, whoever the other person is, within that one mailbox only — never across your other mailboxes or other people’s.
  • Reconnecting keeps your votes. Votes survive reconnecting or re-authorising the same account.
  • Nothing to learn from. A vote on a matter signal, or on a finding read over no account of yours, records your reason but quiets nothing.
Kinds that were quieted by votes counted across the whole workspace before votes became per account may notify again until enough votes on each account build up. Signals Hive withdrew because it lost access to their source (Source disconnected, Member left or Coverage lost) are not dismissals and never count toward alert fatigue. See When Hive loses access to a source.

Dismiss many at once

To clear a batch of noise:
1

Choose Select

Open the ⋯ menu at the end of the filter bar and choose Select. A checkbox appears on every row, and a bar that stays on screen shows 0 selected, Select all, Dismiss and Snooze.
2

Pick the rows

Tick individual rows, or use Select all to select every row currently shown. Use Load more first to include more rows.
3

Choose Dismiss or Snooze

Dismiss asks Why are you dismissing these? with the same four answers as a single dismissal, and applies the one you pick to every selected signal, up to 200 per request. On a row with proposed actions it declines them; nothing is sent. Snooze asks how long, then snoozes each selected signal for that time. A row with proposed actions is snoozed as its own Snooze does, until tomorrow.
Signals that are executing at that moment are skipped. Hive reports how many were dismissed and how many were skipped, so a partial result is never shown as complete. Choose Done to leave select mode.

Manage muted types

Open the ⋯ menu at the end of the filter bar and choose Muted types (n) to open Muted signal types. It opens over the feed, as a sheet on a phone. It lists the active suppressions you can manage and lets you Unmute them:
  • Type mutes apply to the whole workspace, so everyone sees them. Creating or lifting one needs the Admin or Owner role.
  • A mute scoped to a connected account is shown to whoever holds that account now, and only they can lift it.
  • A stopped sender or company is listed as Mail from the address, or Mail from anyone at the domain. It is shown to whoever holds the mailbox it was stopped on, and only they can lift it.
  • Every other mute — by record, by fingerprint or by connection — belongs to the member whose dismissal created it. Only that member sees it in the list and can lift it, because it can name something from a source only they hold. Lifting your own needs Operator or higher.
  • A mute lasts 14 days by default and at most 90 days. There is no permanent mute: to stop Signals raising anything on a matter for good, mute the matter on the Matters tab.
Lapsed suppressions are kept for 30 days for reference and then deleted.

See who closed a signal

A closed signal says who closed it and why, on its row and in its Details: When another member closed a signal you can see, the row says A teammate and never names them. Hive also records when you first see each signal: when at least half of its row has been on screen for a second, or when you open its details. It uses this, with who closed each signal and why, to measure which signals are worth raising. It keeps only the first time per signal, and never shares it with an AI model. Nothing changes on the screen.

Reopen a closed signal

You can reopen a closed signal for 7 days after it was closed, whoever closed it: you, a teammate or Hive. It goes back to your open signals as Needs you, ready to act on again. Reopening does not erase the close: Hive keeps it on record, marked as corrected by you, and stops counting it as the signal’s outcome.
  • After a dismissal. The confirmation that follows Dismiss offers Undo, which reopens the signal.
  • From the signal. Under Done, or wherever a closed signal is shown, its Details say Reopen until and the last day you can, with Reopen beside it. A finding Hive closed as done is reopened from Closed by Hive on the Signals page, even when you had already approved its action before Hive closed it.
  • From an AI client. The signals_reopen tool of the Hive MCP server reopens any signal you can read, and can say why: not done, closed by mistake, or other. Hive keeps that reason on record with the correction.
Hive refuses a reopen, and changes nothing, when:
  • the close is more than 7 days old;
  • Hive withdrew the signal because it lost access to its source, or replaced it with a newer signal;
  • you approved Hive’s action and it already ran, so reopening would ask Hive to do it again;
  • the signal is already open, or an open signal about the same thing already covers it. That one is the signal to work.
Reopening needs the Operator role or higher, as dismissing does, and only works on a signal you can read: a teammate’s private signal stays hidden. It does not lift a mute or a sender stop the dismissal set; lift those under Manage muted types.

How often Hive checks

Hive checks every connected tool once an hour on its own, for every member. Connecting a tool queues a read straight away, ahead of that hourly queue, so the first signals can appear within minutes. Signing up queues the same kind of run, which starts once a tool other than email is connected. For mail and files, the read starts once the first sync has stored something, so an empty check cannot mark the mailbox already read. Owners and Admins see when the next hourly check is due at the top of the Signals page and on the Connectors tab of Integrations. If Hive is already busy, the page says Queued — starts when a slot frees.

Signals overview

What a signal is and how Hive finds it.

Review and approve

Approve, defer or reject what Hive proposes.

Keep an eye on something

Ask Hive to tell you when something happens, and it follows it as a matter.

Troubleshooting

Fix missing or noisy signals.