Notifications
Huntbase notifies you when something needs you, when work you started finishes, and when activity happens in your organisations. Notifications arrive live while you are signed in, and you control which channels and categories you receive from Settings › Personal › Notifications.
Notifications land in your Inbox, which shows those for the organisation you're working in:
- Mentions & assigned holds notifications that name you: a mention or a task assigned to you.
- Updates holds every other notification: runs and exports you started, hunts, watcher events and team activity.
- Done holds the ones you archived.
Both folders show their unread count, but neither adds to the Inbox's main number, which counts only what needs you.
Read and manage notifications
Click a notification to read it; it's marked read at the same time, and its button opens what it refers to (a hunt, a query, an export, an invitation).
- Unread only shows only unread notifications. Mark all read clears the unread ones in the folder.
- Mark unread (u) and Archive (e) act on the open notification. In Done, Restore (e) brings an archived one back.
- ⋯ › Turn off "…" stops that kind of notification in one click. A message confirms it, with Undo and Manage all (your preferences).
- The gear icon opens your notification preferences.
- Load more at the bottom of the list fetches older notifications.
New notifications also appear briefly as a toast in the corner of the screen as they arrive. A repeat about the same hunt replaces its earlier toast instead of stacking, and a hunt's toasts are dismissed when you switch to another hunt; the notification stays in your Inbox.
The bell
In the classic layout, the bell in the page header carries one red badge: the number of items that need you, the same number as the Inbox menu item. Unread notifications don't add to it; when you have some in the organisation you're working in, a small dot shows on the bell instead. With the new navigation there is no bell: the header's Inbox button carries the number.
Click the bell for a peek at Needs you: the top items, each of which opens in the Inbox. Items older than 14 days are summed up in one line. The footer has Open Inbox, Updates with its unread count and, where you have it, Messages.
Live updates
Notifications stream to the app while you are signed in — you do not need to refresh. If your connection drops, Huntbase reconnects and fetches anything you missed in the meantime, so the counts and lists stay accurate.
What triggers a notification
The exact set grows over time, but notifications currently cover:
| Category | Examples |
|---|---|
| Hunt alerts | Hunt being built / ready / couldn't be built, hunt alerts, and watcher events: a watcher started a hunt, created a detection, applied a tag, sent its digest, or was paused for firing too often |
| Scout | Scout progress, finished, failed, or waiting for your input |
| Tasks and queries | Query finished / failed / cancelled, task finished / failed, connection tests |
| Exports | Export ready or failed; the notification links to the pickup page |
| Account and organisation | Organisation invitations, invitations accepted, members joining or leaving, mentions, task assignments, AI credits running low or used up |
| Security | Sign-in from a new device, password changed, two-factor authentication turned off |
Query finished is off by default: queries you run and watch show their results where you ran them. Turn it on in your preferences if you want to hear when a scheduled or long query finishes. It is sent once the run reaches its final state (finished, partly finished or failed), never while it is still collecting results.
Notification preferences
Open Settings › Personal › Notifications (or the gear icon in the Inbox's Updates folder). The page has two parts.

Where notifications go
Each available channel is shown as a card with its status:
| Badge | Meaning |
|---|---|
| On | The channel is set up and can deliver to you. |
| Not set up | The channel needs to be connected first: click Connect [channel] on the card. |
| Not available yet | The channel is planned but not yet available. |
Channels currently include in-app notifications and email, with additional channels shown as they become available for your account.
Presets
Start from a preset sets every notification in one click:
| Preset | What you get |
|---|---|
| Only what needs me | Hunts and findings waiting on you, Scout asking for input, failures and security. No "finished" updates. |
| Recommended | Huntbase's defaults: what needs you, plus failures and a few updates. Finished queries stay quiet. |
| Everything in the app | Every notification in the app, including finished queries and tasks. Email stays as recommended. |
The preset your settings match is highlighted. Change any switch afterwards and none is.
Preferences by category
Below the presets, one list per category (Hunt alerts, Scout, Tasks and queries, Exports, Account and organisation, Security, Inbox) shows each notification with a switch per channel (In-app, Email). On a phone, each notification's switches sit under its name.
- Every switch saves as you flip it. There is no Save button, and nothing is lost if you leave the page. "All changes saved" by the presets confirms it; if a change can't be saved, the switch goes back and a message says so.
- A switch marked Required can't be turned off; Huntbase always delivers that notification on that channel (for example security events by email).
- A switch marked Not set up is off until you connect the channel above.
- Not available means the notification isn't offered on that channel.
- Hunt ready and Hunt couldn't be built can go by email. Hunt ready covers both Hunt plan ready to review (Guide and Collaborator hunts) and Scout finished: Confirmed (draft) — review, sent when Scout drafts its verdict on an Operator hunt.
Alert routing
Organization admins can send alerts to a shared place as well as to each person's own notifications. Open Settings, choose your organization, then Alert routing. There is one card per destination, and on each you tick What to send:
- A watcher started a hunt
- Hunt alerts from integrations
- A detection was quarantined
- Every watcher finding
- Watcher digest
Routing is additive: it never replaces anyone's own notifications. A watcher's Who gets told (on its Deploy tab) lists the destinations its alerts reach; see When this fires.
| Card | Destination |
|---|---|
| Slack channel | A Slack incoming webhook URL (https://hooks.slack.com/services/…). |
| Team mailbox | One email address, such as an on-call mailbox or distribution list. |
| Webhook | Any HTTPS URL that accepts a JSON POST: PagerDuty, Opsgenie, Microsoft Teams (through a workflow), a SOAR or your own service. |
Saved URLs are only ever shown masked.
Send test
Every card has Send test. It goes through the same sender real alerts use and reports what happened:
- Test sent — the destination accepted it. Check the channel, mailbox or receiver.
- An error in red — the destination refused it, with the reason (for example a removed Slack webhook, or the receiver answered 401).
- A neutral note — this environment can't send that kind of message, so nothing was sent. The Team mailbox card also says so up front when email can't be delivered from where Huntbase is running. It is not a fault of your mailbox.
Send test is limited to a few tests per organization every 10 minutes.
Webhooks
Paste the receiver's URL, tick what to send and select Save webhook routing.
- HTTPS only, public addresses only. Huntbase won't post to private, internal or cloud-metadata addresses, checks the address again on every delivery, and doesn't follow redirects: use the final URL.
- Signing secret. Saving a new URL creates a signing secret and shows it once. Copy it into your receiver, then select I've stored it. Huntbase keeps it encrypted and can't show it again. New signing secret replaces it; the old one stops working at once.
- Retries. Each delivery waits up to 10 seconds for an answer. On a timeout,
a connection error,
408,425,429or a5xxit tries twice more, after 2 and 8 seconds. Any other4xxisn't retried. - Send test posts a signed test to the saved webhook, so save a new URL before testing it.
Each request is a POST with Content-Type: application/json and these
headers:
| Header | Value |
|---|---|
X-Huntbase-Event | The alert type, for example watcher_hunt_started, or test. |
X-Huntbase-Delivery | A unique id for the alert. Use it to drop duplicates. |
X-Huntbase-Signature | t=<unix seconds>,v1=<hex HMAC-SHA256> |
The body:
{
"id": "6f1c…",
"type": "watcher_hunt_started",
"test": false,
"created_at": "2026-11-01T09:30:00+00:00",
"org_id": "b993…",
"title": "Watcher started a hunt: Scheduled task created from the command line",
"text": "Triggered by the Scheduled task created from the command line watcher",
"priority": "high",
"url": "https://app.huntbase.io/hunts/…",
"resource": { "type": "hunt_session", "id": "…" },
"data": { "watcher_name": "…", "watcher_slug": "…" }
}
To verify a request, compute HMAC-SHA256 with your signing secret over the
timestamp, a full stop and the raw body (<t>.<body>), compare it with v1,
and reject requests whose t is more than a few minutes old:
import hashlib, hmac, time
def verify(secret: str, header: str, body: bytes, tolerance: int = 300) -> bool:
parts = dict(p.split("=", 1) for p in header.split(","))
expected = hmac.new(
secret.encode(), f"{parts['t']}.".encode() + body, hashlib.sha256
).hexdigest()
fresh = abs(time.time() - int(parts["t"])) <= tolerance
return fresh and hmac.compare_digest(expected, parts["v1"])
For PagerDuty or Opsgenie, point the webhook at a small function (or your SOAR)
that verifies the signature and maps title, priority and url onto the
service's own event format.
Next steps
- Watchers — standing rules that raise detections and start hunts
- Personal settings — profile and sign-in security
- Hunts — what "hunt ready" notifications point to
- Activity — everything that happened, in one place
- Inbox — where notifications, messages and what needs you land