Acting on, snoozing and dismissing signals needs the Operator role or higher. Analysts can read every
signal and the reasoning behind it, but cannot change it. See Roles and permissions.
Find what needs you
Open Signals from the sidebar. The Attention tab has three views:
Narrow any view with the severity chips (All, High, Medium, Low) or Search signals…, which
searches the signal type, the entity and the explanation (up to 120 characters). The feed loads 50 rows at a time;
use Load more for the rest. Counts always reflect everything that matches, not just the loaded rows.
Your filters 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.
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.
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 where an earlier preparation failed.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 the plan is approved (or is within an autonomy level your workspace has granted — see
Autonomy and blast radius).
3
If preparation fails
Choose Retry preparation to try again.
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
Dismiss: say why
Choose Dismiss when a signal is not useful. Hive asks Why are you dismissing this?, and the reason you pick decides what changes about future detection:
The confirmation always states what actually happened. If you are not an Owner or Admin and pick This is
expected — mute this type, the toast tells you it was counted as feedback rather than a workspace mute.
How dismissals reduce noise over time
Dismissals marked Not relevant to us or Wrong — this isn’t happening feed Hive’s alert-fatigue gate. When at least five signals of one type have been surfaced in the last 14 days and your team has dismissed 80% or more of them, Hive stops notifying about that type. This lifts automatically as those dismissals age past 14 days, so a type your team muted by feedback can come back if the situation changes.Dismiss many at once
To clear a batch of noise:1
Choose Select detections
Checkboxes appear on each row.
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 selected
Hive dismisses up to 200 signals per request.
Manage muted types
Select Muted (n) to open Muted signal types. It lists every active suppression — by type, by record, by fingerprint, or by connection — and lets you Unmute any of them.- Creating a workspace-wide type mute needs the Admin or Owner role.
- Lifting a suppression needs Operator or higher.
- A mute lasts 14 days by default and at most 90 days. There is no permanent mute: to stop watching something for good, turn off the metric on the Coverage tab, where the change stays visible.
Run the loop now
Hive checks your tools every hour. Owners and Admins can start a check immediately with Run loop now at the top of the Signals page, for example right after connecting a new tool. The timer next to it shows when the next scheduled run is due.Related
Signals overview
What a signal is and how Hive finds it.
Review and approve
Approve, defer or reject what Hive proposes.
Coverage
Check what Hive is watching before trusting a quiet feed.
Troubleshooting
Fix missing or noisy signals.