> ## Documentation Index > Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt > Use this file to discover all available pages before exploring further. # Triage signals: act, snooze or dismiss > Work the Signals feed: filter it, ask Hive to act, snooze with confidence, dismiss with a reason, bulk-dismiss noise and manage muted types. 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. **Analysts** can read every signal and the reasoning behind it, but cannot change it. See [Roles and permissions](/admin/roles-and-permissions). ## Find what needs you Open **Signals** from the sidebar. The **Attention** tab has three views: | View | Shows | | - | - | | **Action needed** | Signals in the **Needs you** stage. | | **Updates** | Signals Hive is working on, watching, or that are snoozed. | | **All** | Everything open. | 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](/approvals/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. The row changes to **Asking Hive…** and then "Preparing a response". Your request has been accepted; it has not run yet. 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](/approvals/autonomy-and-blast-radius)). Choose **Retry preparation** to try again. 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. ## 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. ## 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: | Reason | What Hive does | Confirmation | | - | - | - | | **Already handled** | Stays quiet about this record. | "Dismissed — Hive will stay quiet about this record." | | **Duplicate of something else** | Stays quiet about this record. | Same as above. | | **This is expected — mute this type** | Stops raising this type of signal for the whole workspace (Owners and Admins). For other roles it counts as the "not relevant" vote below. | "Dismissed — Hive will stop raising this type for your workspace." | | **Not relevant to us** | Counts toward alert fatigue for this type. | "Dismissed — noted. Hive raises this type less once enough of you say the same." | | **Wrong — this isn't happening** | Counts toward alert fatigue for this type. | Same as above. | | **The underlying data is wrong** | Stays quiet about this record, and blames the data rather than the detector. The connection itself is not muted. | "Dismissed — the connection behind it is flagged for a look, not the detector." | | **Wrong record** | Stays quiet about this record. The connection itself is not muted. | Same as above. | | **Just dismiss it** | Closes this signal only. | "Dismissed — nothing changed 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. For mail signals, "stay quiet about this record" means this conversation thread, not every thread with that person. ### 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: Checkboxes appear on each row. Tick individual rows, or use **Select all** to select every row currently shown. Use **Load more** first to include more rows. Hive dismisses up to 200 signals per request. 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. ## 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](/signals/coverage) tab, where the change stays visible. Lapsed suppressions are kept for 30 days for reference and then deleted. ## 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 What a signal is and how Hive finds it. Approve, defer or reject what Hive proposes. Check what Hive is watching before trusting a quiet feed. Fix missing or noisy signals.