> ## Documentation Index
> Fetch the complete documentation index at: https://docs.borghq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Alert Centre

> Stay on top of security events with in-app notifications

The Alert Centre is your in-app notification inbox. It surfaces events across your organisation: new findings, status changes, completed reports, new assets discovered, team changes, and more.

Open the Alert Centre by clicking the bell icon in the top navigation bar. The bell shows a red indicator when there are unread notifications.

## Notification types

Odin generates notifications for the following events:

| Event                         | Description                                                     |
| ----------------------------- | --------------------------------------------------------------- |
| **New finding created**       | A new security finding has been identified                      |
| **Finding status changed**    | A finding's status was updated (e.g. Reported → Mitigating)     |
| **Finding assigned**          | A finding was assigned to you                                   |
| **Report delivered**          | A new pentest report revision is ready to view                  |
| **Pentest status changed**    | A pentest engagement started, completed, or changed state       |
| **New asset discovered**      | Continuous Asset Discovery found a new domain, subdomain, or IP |
| **CAD scanning paused**       | Continuous Asset Discovery scanning was paused on an asset      |
| **CAD scanning resumed**      | Scanning has resumed on an asset                                |
| **Mjolnir run paused**        | A Mjolnir run was paused mid-flight                             |
| **Integration token expired** | An integration's OAuth token expired and needs reconnecting     |
| **Discussion message**        | Someone replied or mentioned you in a finding discussion        |
| **Member joined**             | A new member joined the organisation                            |
| **Member left**               | A member was removed or left                                    |
| **Member role changed**       | A member's role was updated                                     |

<Info>
  Finding-related notifications — **New finding created**, **Finding status changed**, and **Discussion message** — go to that finding's [followers](/platform/findings#following-findings), not the whole organisation. See [Default finding subscribers](/platform/organisation-settings#default-finding-subscribers) for who follows a finding by default.
</Info>

<Note>
  [Following a finding](/platform/findings#following-findings) — by clicking **Follow**, commenting on it, being `@mentioned`, or being assigned — means status changes and discussion replies on it arrive as immediate Alert Centre entries. If you've only been subscribed automatically as a [default subscriber](/platform/organisation-settings#default-finding-subscribers) and haven't otherwise engaged with the finding, its routine updates arrive in your [weekly summary](#weekly-summary) instead. Assignment and @mentions always send an immediate alert.
</Note>

## Grouped notifications

When several findings are reported or updated at once — for example when a pentest report is delivered — the Alert Centre shows a single grouped entry instead of one notification per finding, such as "12 findings reported".

Select **Show findings** on a grouped entry to expand the list of findings it covers. Each one links through to the finding itself.

## Weekly summary

Odin bundles status changes and discussion replies into a weekly summary — one email plus a matching Alert Centre entry — recapping activity across every finding you follow.

* **When it arrives**: Monday morning, covering the previous week's activity.
* **What it covers**: status changes and discussion replies across every finding you follow. It's the primary way you'll hear about findings where you're only a [default subscriber](/platform/organisation-settings#default-finding-subscribers) and haven't otherwise engaged, since those don't send an immediate alert.
* **What's excluded**: assignments and @mentions always send an immediate alert and are never held back for the weekly summary.
* **Opting out**: turn off the weekly summary from your [profile](/platform/profile#weekly-summary).

## Email notifications

On top of the Alert Centre, a few events also send an email, so you don't need to be watching the inbox to catch them:

* **Assigned to you**: you're emailed when a finding is assigned to you.
* **Retest failed**: if a finding assigned to you is retested and moves to **Needs Revision**, you're emailed.
* **Critical in a delivery**: when a batch of newly reported findings includes at least one **Critical**, your organisation's [default finding subscribers](/platform/organisation-settings#default-finding-subscribers) are emailed.
* **Weekly summary**: a Monday-morning email recapping routine activity on every finding you follow — see [Weekly summary](#weekly-summary) above.

Every other notification type — the rest of the events listed above — stays in the Alert Centre only, with no separate email. This includes routine status changes and discussion replies: if you [actively follow](/platform/findings#following-findings) the finding, you get an immediate Alert Centre entry; if you're only a default subscriber who hasn't otherwise engaged with it, the update is rolled into the weekly summary instead. Assignments and @mentions are the exception — they always notify you immediately and by email.

## Slack notifications

If you've connected Slack, the connected channel receives **new findings**, **retest failures**, and **finding assignments**, plus a single **weekly summary** post covering that week's digest. Routine status changes and discussion replies on findings you follow — whether from your organisation's members or the Borg security team — don't post to Slack individually; they're covered by the weekly summary post instead. The other notification types above stay in the Alert Centre only.

From **Management > Integrations**, the Slack card's **Channel overrides** let you route individual notification types to a channel other than your default — for example, sending **Finding assigned** posts to a separate channel from new findings and status changes.

## Filtering

Use the tabs at the top to switch between **All** notifications and **Unread** only. The unread tab shows a count so you can see how many items need attention.

## Managing notifications

* **Mark as read**: hover an unread notification and click the tick icon to mark it read without leaving the inbox
* **Mark all as read**: the button above the list clears every unread notification in one go, and greys out when you have nothing unread
* **Mark several at once**: hover a notification to reveal its checkbox, tick the ones you want, then choose **Mark selected as read**. Use **Clear selection** to drop your picks without changing anything
* **Click to navigate**: clicking a notification opens the item it refers to (a finding, report, Mjolnir run, or asset) and marks it read on the way through