Notifications

Hydrant notifies you about nine 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.
Waiting for your approval	An issue lands in an environment you approve: finished into it, moved there, or promoted. It reads like “Sam sent this to Staging for your approval”. A promotion that leaves two or more issues waiting for you sends one notification instead, like “Sam promoted 25 issues to Staging”, which opens the list of issues waiting for you there; the email digest counts how many still wait.
Waiting for your review	An issue lands in a review stage that names you as a reviewer. It reads like “Sam sent this to Human Review. Your call.” A stage that names nobody sends nothing, and you never hear about a move you made yourself.
Sent back	A reviewer sends back an issue assigned to you, or to an agent you own. It quotes the first line of their note and opens it. You get this instead of Comment on assigned for that note.
Replies to your comments	Someone answers a comment thread you started or wrote in. It reads like “Sam replied to your comment” and jumps to the reply. If the same reply also mentions you or lands on an issue assigned to you, you get only that one. Only what you wrote yourself counts: a thread only your agents wrote in doesn’t.
Issues you follow	An issue you follow moves to another stage, including Done and Canceled, or gets a comment. It reads like “Sam moved this to Human Review”. If the same change already told you something else, such as a mention, you get only that one.

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)”.

Follow an issue

Follow an issue to hear about it without being assigned. Press the bell next to Copy issue link at the top of the issue, or choose Follow from a row’s menu. Pressed means you follow it; press again, or choose Unfollow, to stop.

• You follow an issue automatically when you create it or comment on it. Once you unfollow, commenting again doesn’t follow you back.
• Nobody else sees who follows what, and following never changes the issue.
• Agents never follow anything automatically. A connected agent can follow or unfollow an issue for the person who connected it.
• The Following filter in an issue list shows what you follow.

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 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 › Notifications.
2. Under What reaches you, each event has two checkboxes, grouped into Waiting on you and Keeping you posted:
   • In-app: whether new ones land in your bell.
   • Email digest: whether that event appears in the daily digest email.
3. Tick or clear one. 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, Assignment, Waiting for your approval, Waiting for your review, Sent back and Replies to your comments start on, and Unblocked, Comment on assigned and Issues you follow start off. If you had switched every event off for a channel, a new one stays off there too.

The digest arrives each morning around 08:00 in your timezone, and only when there’s something in it.

Look back at your week

Last week’s recap on the full notifications page shows last week (Monday to Monday, in your timezone) across every workspace you belong to:

• Accepted: issues you moved to Done yourself. An agent moving one on your key doesn’t count.
• Your agents shipped: Done work assigned to agents you own. An issue your agent shipped and you accepted appears in both lists.
• Closed out: projects completed and milestones achieved.

When the week earns it, one line says so, like “Biggest week since August”. There are no streaks and no comparisons downward.

The same recap can arrive by email on Mondays from 08:00 in your timezone, and only when there’s something in it. That’s the Timezone in Settings › Preferences: the one you chose, or in Automatic, wherever you last opened Hydrant. Nothing reported yet means UTC. It follows the Weekly recap switch in Settings › Notifications, which starts on. The email’s Stop weekly recaps link lets you stop them without signing in.

Stop recurring emails

Open Stop weekly recaps or Stop digest emails in an email, then press Cut the recap or Stop digest emails. No sign-in is needed. Opening or previewing the link alone changes nothing. Your mail app may also offer its own Unsubscribe action.

This stops that email category across your account. Stopping digests clears every Email digest checkbox. Your other email category, in-app notifications and transactional emails are unaffected. A message already on its way may still arrive.

To turn emails back on, sign in and use Settings › Notifications. Stop links expire after 60 days and may become invalid sooner after a security-key rotation; use Notifications if the link no longer works. A forwarded link still controls the original recipient’s subscription, and an unexpired old link can stop it again after re-enable.

What you should see

A bell count that only moves when someone mentions you, hands you work, comments on your work, clears your path, sends you something to approve or review, sends your work back, answers your comments or moves something you follow. 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 nine 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 make the change again.
• A notification links to an issue you can’t open. It was trashed or deleted, or you lost access.

Notifications on this browser

In Settings › Notifications, Notify me here controls this browser. Turn on asks your browser for permission. If closed-tab delivery is available, it explicitly connects this browser for your current account and sign-in session, across your workspaces. Alerts may take a few minutes; browser or OS delivery can take longer. Previews say “You have new activity.” Open Hydrant for details. Clicking opens an authenticated inbox and does not mark anything read.

An existing open-tab choice keeps working until you explicitly choose Enable closed-tab alerts. With push unavailable, open-tab notifications still work, including in the background. The In-app column picks the event families for both modes. Turn off keeps your inbox and email preferences. Blocked permission needs changing in this site’s browser settings. An expired session needs sign-in and Reconnect; clearing site data needs fresh opt-in. If a change cannot be confirmed, retry turning it off. Sign-out attempts cleanup but a reminder already accepted by the push service may still appear. Nothing guarantees OS delivery; the inbox is the record.