# Notifications

What makes Hydrant notify you, where notifications show up, and how to read, snooze, delete and tune them.

Hydrant notifies you about four things, and none of them is "someone looked at a dashboard". If the bell has a number on it, something actually concerns you.

## Before you start

- You're a person in the workspace. Notifications go to people only; agents don't get an inbox.
- Notifications are per workspace. The bell shows the workspace you're in.

## Steps

### Know what triggers one

| Event | You get it when |
| --- | --- |
| **Mention** | Someone @mentions you in an issue description or a comment. |
| **Assignment** | Someone makes you the assignee, including on a brand-new issue. |
| **Comment on assigned** | Someone comments on an issue assigned to you. If the comment also @mentions you, you get the mention, not both. |
| **Unblocked** | A blocker on an issue assigned to you is finished: moved to Done or Canceled, or into Trash. |

Your own actions never notify you, and neither do agents acting on your behalf. When someone else's agent does something, the notification names the agent and the person who connected it, such as "Build Bot (agent; via Sam)".

To mention someone, type `@` and part of their name in a description or comment, then pick them from the list.

### Open the bell

1. Press the bell in the top bar. A count means unread notifications.
2. Each row says who did what and on which issue, like "Sam assigned you, #42 Fix the login loop".
3. Click a row to open the issue. Comment notifications jump straight to the comment. Opening an unread notification marks it read.
4. **View all notifications** at the bottom opens the full page.

The full page has three filters (type "notifications" in [Find it](/help/using/find-your-way#find-it) to get there directly): **All**, **Unread** and **Snoozed**. All lists unread first, then everything else grouped under **Today**, **Yesterday**, **Earlier this week** and **Older**. **Load more** reaches further back.

### Triage

- **Mark all read** clears the unread count in one go.
- Each row's **⋯** menu has **Mark read** or **Mark unread**, **Snooze** and **Delete**.
- **Snooze** offers **In 3 hours**, **Tomorrow** (9:00), **Next week** (Monday, 9:00) or **Custom…** for any date and time within a year. Times use your timezone under **Settings › Preferences**.
- A snoozed notification disappears from the lists and the count, then returns **unread** when it wakes. Find sleeping ones under **Snoozed**, where **Unsnooze** brings one back now.
- **Delete** removes it. **Undo** restores it, but only within an hour. After that it's gone for good.

### Choose what you get

1. Open **Settings › Preferences** (or **Preferences** from the account menu).
2. Under **Notifications**, each event has two switches:
   - **In-app**: whether new ones land in your bell.
   - **Email digest**: whether that event appears in the daily digest email.
3. Flip a switch. It saves straight away.

These settings belong to your account and apply in every workspace. Turning off **In-app** stops new notifications of that kind; it doesn't remove ones you already have.

Out of the box, every event is on for **In-app**. For **Email digest**, **Mention** and **Assignment** start on, and **Unblocked** and **Comment on assigned** start off.

:::note[The digest isn't sending yet]
The daily digest email isn't switched on. Your **Email digest** choices are saved, so they apply the day it is. Until then, the bell is the whole story.
:::

## What you should see

A bell count that only moves when someone mentions you, hands you work, comments on your work or clears your path. When it's empty: "All caught up. Nothing unread. Suspiciously productive."

## If it goes sideways

- **Expected a notification and got nothing.** Check it's one of the four events, that you didn't do it yourself, and that its **In-app** switch is on. Assignment and unblocked notifications only go to people, never to agents.
- **The count seems wrong.** Snoozed notifications don't count until they wake. Deleted ones never count.
- **"Couldn't undo. It may already be back, or the hour to undo has passed."** Either it was already restored, or the hour ran out.
- **"Couldn't update the notification."** The connection dropped. Press **Retry**. It resends the same request, so nothing happens twice.
- **"Could not save notification preferences."** Refresh the page and flip the switch again.
- **A notification links to an issue you can't open.** It was trashed or deleted, or you lost access.

Contact: bots@hydrant.dev