# Set up Pro notifications | bbradar.io

> Understand Telegram, Discord, event streams, opportunity and dupe-risk filtering, and which setup fits your workflow.

Source: [https://bbradar.io/docs/notifications](https://bbradar.io/docs/notifications)

<a id="channels"></a>

## [Choose a channel](https://bbradar.io/docs/notifications.md#channels)

Telegram: personal alerts

Private direct messages filtered by your own notification rules. Telegram is the best choice when you want selected platforms, program tiers, target scores or labels, dupe-risk levels, rewards, or change types.

Discord: shared Pro access

A Pro role in the bbradar community server with shared channels. Discord messages are not personalized by your Telegram notification rule.

| Capability | Telegram | Discord |
| --- | --- | --- |
| Delivery | Private 1:1 bot chat | Shared server channels |
| Personal filters | Yes | No |
| Connection | Single-use bot start link | Discord OAuth and server role |
| Best for | Focused, actionable alerts | Community and broad shared updates |

<a id="event-streams"></a>

## [Choose event streams](https://bbradar.io/docs/notifications.md#event-streams)

| Stream | What it means | Default |
| --- | --- | --- |
| New | A newly launched current program. | On |
| Upcoming | A future-dated program visible to Pro. | On |
| Older | An existing program discovered after its launch. | On |
| Suspended | A program became unavailable or inactive after stability checks. | On |
| Reactivated | A previously inactive program returned. | On |
| Target changes | Material additions, updates, re-additions, and confirmed removals. | On |
| Repository changes | Hourly digest of supported repository branch updates. | Off (opt in) |
| Self-Hosted bounties | A newly verified paid program operated directly by an organization. | On |
| Self-Hosted VDPs | A new disclosure policy with no monetary reward. | Off (opt in) |

Repository alerts are opt-in

The repository-change switch starts off. Enable it in Notification Rules if source-repository changes are part of your workflow.

<a id="recommended-setup"></a>

## [Recommended setup](https://bbradar.io/docs/notifications.md#recommended-setup)

1. ### Connect Telegram

   Use it as your personal, high-signal alert channel.
2. ### Start with filtered mode

   Select the platforms or scope types you actively research, then add opportunity signals and exclusions only where they improve the result.
3. ### Enable repository changes deliberately

   This stream can be busy. Turn it on only if branch activity is useful to you.
4. ### Choose Self-Hosted coverage

   Paid Self-Hosted programs start on; VDP notifications are separate and opt-in.
5. ### Connect Discord if you use the community

   The Discord role complements Telegram; it does not replace personal filters.

<a id="delivery-behavior"></a>

## [Delivery behavior](https://bbradar.io/docs/notifications.md#delivery-behavior)

Telegram and Discord alerts can arrive shortly after an event appears on bbradar. Temporary delivery failures are retried automatically. If you block the Telegram bot, reconnect it before expecting new private alerts.

Target changes and repository changes are separate streams. Enable each one you want, and use the Commits feed when you need to review repository activity directly in the browser.

[Connect TelegramLink and verify a private chat.](https://bbradar.io/docs/notifications/telegram.md)[Build your rulesControl streams and matching behavior.](https://bbradar.io/docs/notifications/rules.md)