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

# How to configure notifications

> Choose which BattleTest events notify you — PR reviews, live scans, and confirmed vulnerabilities — across email, browser push, and in-app channels.

BattleTest can notify you per event, per channel. Configure everything at [Settings → Notifications](https://battletest.dev/settings?tab=notifications).

## Channels

| Channel    | Where it arrives                                                          |
| ---------- | ------------------------------------------------------------------------- |
| **Email**  | Your account email address                                                |
| **Push**   | Browser push notifications (requires granting permission in your browser) |
| **In-app** | The notification bell in the dashboard                                    |

The GitHub PR comment is always posted regardless of these settings — it is the primary output of a PR review, not a notification channel.

## Events you can subscribe to

| Event                    | Fires when                                                 |
| ------------------------ | ---------------------------------------------------------- |
| **PR Review completed**  | A PR review finishes (with or without findings)            |
| **PR Review failed**     | A PR review fails due to an internal error                 |
| **Battletest completed** | A live battletest run finishes                             |
| **Battletest failed**    | A live battletest run fails                                |
| **Vulnerability found**  | A new CRITICAL or HIGH finding is confirmed in a live scan |

## Turn a notification on or off

<Steps>
  <Step title="Open the Notifications tab">
    Go to [Settings → Notifications](https://battletest.dev/settings?tab=notifications).
  </Step>

  <Step title="Toggle the channel for an event">
    Each event has an email, push, and in-app toggle. Switch the channel on or off for that event.
  </Step>
</Steps>

## Enable browser push

<Steps>
  <Step title="Toggle push on for any event">
    The first time you enable a push toggle, your browser asks for notification permission.
  </Step>

  <Step title="Allow notifications">
    Click **Allow**. If you previously blocked notifications for the BattleTest domain, re-enable them in your browser's site settings first, then toggle push again.
  </Step>
</Steps>

## Push findings to Slack, PagerDuty, or your own systems

Per-channel notifications are for humans. To route events into other tools — Slack alerts, PagerDuty incidents, ticket creation — use outbound webhooks instead. See [How to send findings to external tools](/docs/how-to/send-findings-to-external-tools).

## Not receiving emails?

Check your spam folder — the first email from `noreply@battletest.dev` is sometimes filtered. Add the address to your contacts. See [Troubleshooting](/docs/how-to/troubleshooting#im-not-receiving-battletest-email-notifications) if it persists.