Overview

Flarehawk sends notifications whenever a detection rule fires an alert. You can receive those notifications across multiple channels simultaneously — email, Slack, and webhooks — so the right people and tools are reached no matter where your team works. This page explains how notifications work, where to configure them, and how to prevent alert fatigue with severity filters and deduplication.

​

Available channels

Flarehawk supports three notification channels: You can enable any combination of channels. Each channel has its own severity filter, so you can route only critical alerts to Slack while sending all severities to email.

​

Accessing notification settings

To configure notifications, open Settings in the Flarehawk dashboard and select the Notifications tab. From there you can:

• Enable or disable each channel
• Add and remove recipients
• Set per-channel severity thresholds
• Send a test notification

To connect Slack or review integrations, go to Settings → Integrations.

​

Notification preferences

​

Severity levels

Flarehawk alerts carry one of four severity levels: For each channel you can set a minimum severity threshold. Alerts below that threshold are not delivered on that channel. For example, setting Slack to high means only high and critical alerts are posted to your Slack channel, while email still receives everything at medium and above. You can also set a global minimum severity that applies to all channels unless overridden per channel.

​

Quiet hours

You can define a quiet hours window during which notifications are suppressed on selected channels. Quiet hours are configured with a start time, end time, and timezone. Alerts that fire during quiet hours are not delivered — they are not queued for later delivery.

​

Deduplication

Flarehawk uses cooldown windows to prevent alert spam. When a detection rule fires repeatedly for the same domain, subsequent alerts are deduplicated within the cooldown window configured on that rule. Only the first alert in each window triggers a notification. This means your inbox and Slack channel stay actionable without being flooded when a rule enters a repeated firing state.

​

Testing notifications

You can send a test notification from Settings → Notifications to verify that a channel is configured correctly. The test sends a sample alert payload to all enabled channels. Use this after adding a new email recipient, connecting Slack, or configuring a webhook endpoint.

​

Plan availability

Email, Slack, and webhook notifications are included on every Flarehawk plan, from Free to Enterprise.

​

Next steps