# Build notification rules | bbradar.io

> Filter Telegram alerts by platform or Self-Hosted stream, opportunity, target score, dupe risk, scope, reward, and saved exceptions.

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

<a id="rule-modes"></a>

## [Choose a rule mode](https://bbradar.io/docs/notifications/rules.md#rule-modes)

Every edit remains a draft until you save it. Use this sequence for a complete rule:

1. ### Open Notification Rules

   Open [Notification Rules](https://bbradar.io/account/notifications) from Account & Billing.
2. ### Choose Everything or Filtered

   Use Everything for broad delivery, or Filtered when platforms, rewards, submission fees, opportunity signals, and include or exclude rules should participate in matching.
3. ### Choose event streams

   Enable only the platform-program, lifecycle, target, repository, Self-Hosted bounty, or Self-Hosted VDP events you want. Repository changes and Self-Hosted VDPs are opt-in.
4. ### Keep Telegram DM enabled

   The rule controls private Telegram delivery. Discord channels are shared and do not use this page.
5. ### Review the Current rule preview

   Check the mode, streams, platforms, tags, languages, opportunity selections, target types, bounty, and submission-fee summary.
6. ### Select Save Rules

   Wait for the **Rules saved** confirmation. Navigating away before saving discards the draft.

The selected mode changes how the saved rule is evaluated:

| Mode | Behavior | Use it when |
| --- | --- | --- |
| Everything | All enabled event streams can be delivered. | You want broad coverage and do not need platform or target filters. |
| Filtered | An enabled event must also match your saved rule. | You want focused alerts based on your research interests. |

Note

Notification rules personalize Telegram only. Discord uses shared server channels.

[Open Notification RulesBuild, preview, and save your private Telegram rule.](https://bbradar.io/account/notifications)

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

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

Enable New, Upcoming, Older, Suspended, Reactivated, Target changes, Repository changes, Self-Hosted bounties, or Self-Hosted VDPs independently. Repository changes and Self-Hosted VDPs start disabled; verified paid Self-Hosted program alerts start enabled.

Sanitized product view

Notification Rules

Alert only when a saved rule matches

Pro

Rule mode

EverythingFiltered

Event streams

✓ New✓ Target changes✓ Repository changes

Filters

Programs: Elite or HotTarget score: 70+Target: Strong TargetDupe risk: LowPlatform: HackerOneExclude: *.staging.test

Save Rules

Filtered Telegram rule using program opportunity, target score, and dupe risk. Example data and credentials are fictional or redacted; named product controls match the interface.

For target changes, you can further select Added, Updated, Removed, and **New scope only**. The target-type filter can narrow alerts to domains, mobile apps, source-code targets, smart contracts, IP ranges, and other supported target categories.

<a id="filters"></a>

## [Add filters](https://bbradar.io/docs/notifications/rules.md#filters)

In Filtered mode, selected values inside one filter group are alternatives, while different filter groups must all match. For example, Elite or Hot programs can be combined with a minimum target score of 70 and Low dupe risk.

| Filter | What it matches |
| --- | --- |
| Platforms | Any of the 25 supported platform names, plus Self-Hosted. |
| Scope tags | Program and target tags such as web, mobile, API, source code, or smart contract. |
| Languages | Languages associated with the program or its repository targets. |
| Program opportunity | Elite, Hot, Strong, or Potential for the program attached to an alert. |
| Target opportunity | Elite Target, Strong Target, Potential Target, or Normal for each changed or repository-mapped target. |
| Minimum target score | A 0–100 threshold applied to each changed or repository-mapped target. |
| Dupe risk | Low dupe risk, Medium dupe risk, High dupe risk, or Unknown dupe risk for target and repository alerts. |
| Bounty range | Minimum and/or maximum advertised reward bounds. |
| Submission fee | Free only, paid only, or both, with an optional maximum fee or deposit. Missing platform cost data is treated as free. |
| Target changes | Added, updated, removed, and new-scope-only selections. |
| Target types | The target category shown by bbradar. |
| Program include/exclude | Exact saved programs that override or block other matching. |
| Target include/exclude | Identifier patterns used to override or block selected target matching. |

For a fee range or refundable deposit, the maximum possible amount is compared with your limit. USD and USDC use the displayed $ amount; credit-based platforms use their displayed credit amount.

<a id="opportunity-signals"></a>

## [Filter by opportunity and dupe risk](https://bbradar.io/docs/notifications/rules.md#opportunity-signals)

Program and target opportunity are separate signals. A program tier ranks the parent program; a target label and score rank one changed or repository-mapped target.

| Signal | Values | Applies to |
| --- | --- | --- |
| Program opportunity | Elite, Hot, Strong, Potential | Program alerts and the parent program on target or repository alerts. |
| Target opportunity label | Elite Target, Strong Target, Potential Target, Normal | Each target in Target changes and each mapped target in Repository changes. |
| Minimum target score | Any whole number from 0 to 100 | Each target in Target changes and each mapped target in Repository changes. |
| Dupe risk | Low, Medium, High, Unknown | Target and repository alerts. Higher risk means more visible crowding or duplicate pressure. |

| Target label | Score band |
| --- | --- |
| Elite Target | 85–100 |
| Strong Target | 70–84 |
| Potential Target | 50–69 |
| Normal | 0–49 |

Use target scores and dupe risk as comparative research aids, not predictions. **Unknown** means there is not enough public data for a reliable estimate; it does not mean low risk.

Grouped target alerts show only matching targets. Repository alerts are delivered when at least one linked program target matches the complete rule.

Missing signals do not match

Selecting a minimum score, target label, program tier, or dupe-risk value excludes an alert when the required signal is unavailable or does not match. Leave a group on All or Any if you do not want it to narrow delivery.

<a id="overrides"></a>

## [Understand include and exclude overrides](https://bbradar.io/docs/notifications/rules.md#overrides)

In filtered mode, exclusions always win. Includes are overrides, not allowlists:

- An excluded program never matches.
- An excluded target never matches.
- An included program bypasses matching filters, but not the enabled stream, selected target-change types, New scope only, or exclusions.
- An included target bypasses scope, language, target-type, minimum-score, target-opportunity, and dupe-risk filters.
- Platform, reward bounds, submission fee, parent-program opportunity, stream, target-change type, and New scope only still apply to an included target.

Pattern strategy

Start with broad platform and reward filters, then exclude noisy staging or documentation targets. Use includes only for exceptions you never want to miss.

<a id="examples"></a>

## [Example rules](https://bbradar.io/docs/notifications/rules.md#examples)

| Goal | Suggested rule |
| --- | --- |
| Fresh web scope | Filtered mode; Target changes on; Added and New scope only; target types Domain and URL; exclude known staging patterns. |
| High-value programs | Filtered mode; select Elite or Hot program opportunity; set a minimum bounty and an acceptable maximum submission fee; include one or two must-watch programs as explicit exceptions. |
| Fresh target opportunities | Target changes on; Added selected; minimum score 70; Elite Target or Strong Target; Low dupe risk. |
| Repository movement | Repository changes on; select relevant platforms plus a minimum score, target opportunity, or dupe risk; each mapped target must satisfy the selected target signals. |
| New paid Self-Hosted programs | Self-Hosted bounties on; Self-Hosted selected as the platform; add reward bounds only if you need them. |
| Self-Hosted disclosure policies | Self-Hosted VDPs on; Self-Hosted selected as the platform. VDPs have no confirmed monetary reward and are opt-in. |
| One program exception | Keep your normal filters and add that program to Included programs. |

After changing any field, select **Save Rules** and wait for the saved confirmation. Prefilling a rule from a program page does not save it automatically.
