> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/configuration/configuration-notifications.md).

# Notifications

Notification rules pair **events** with **targets**. Configure them through the tenant's integration settings or `GET`/`PUT /admin/integrations/notifications`.

## Event filters

Each rule's `events` object selects one or more event types: `all`, `newCodeFindings`, `newDependencyFindings`, `newSecretFindings`, `newApiFindings`, `newSupplyChainFindings`, `newCloudFindings` and `threatIntel`. A rule that names no event type matches every type except cloud findings. Cloud findings are delivered only to a rule that sets `newCloudFindings`; `all` does not include them.

Filters vary by event type. Supported fields include repository selection, minimum severity/priority, CWE IDs, CVE IDs, secret types, cloud providers, and supply-chain finding types. Use the schema for the selected event instead of sending every filter to every event. Narrow filters can intentionally suppress delivery while findings remain visible in the dashboard.

## Destinations

The generic target model has Slack channels, email addresses, and webhook URLs, with singular and plural forms supported by the corresponding schema. Microsoft Teams conversations use the Teams integration; a Teams destination is not an extra `teams` property in the generic notification-target object.

`centralSecurityChannel` is a fallback destination for action items without a resolved owner. In the Slack connector's settings it is the **Alerts channel ID**. Configure it deliberately and ensure the integration can post there. Confirm user identity mappings before relying on direct messages.

## Status updates and threat results

**Settings → Ways of working → Status updates** sends progress on campaign goals and the security program, plus pull requests, default-branch changes and new threat investigations, to the Slack and Microsoft Teams channels configured for the workspace. The **Daily update** covers the previous UTC day plus current coverage and outstanding work; the **Weekly update** is sent on Monday for the previous Monday–Sunday in UTC. Both are off by default; the API fields are `dailyUpdatesEnabled` and `weeklyUpdatesEnabled` on `PUT /admin/manager/settings`.

<figure><picture><source srcset="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-598afd1a6470cc2ca1319c2415534bf1af08142b%2Fstatus-updates-settings-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-ef4f68abdaa2cc819ebca340ba78e0fad35fc94d%2Fstatus-updates-settings.png?alt=media" alt="Daily and weekly update toggles"></picture><figcaption><p>Weekly on, daily off.</p></figcaption></figure>

Threat investigation results use their own destinations under **Settings → Assessments → Threat investigations → Where results are sent**: the shared Slack Connect channel with Nullify (on by default, but delivered only when the **Threat investigation shared-channel messages** capability is turned on, which is off by default), a channel ID in your connected Slack workspace, and a Microsoft Teams incoming-webhook or Workflows URL.

## Delivery controls

Manager escalation delivery can enforce weekly channel/DM budgets, content deduplication, and digest grouping. Critical-severity bypass rules apply where configured. Failed channel delivery can fall back to a recovery DM when a suitable recipient is available. These controls mean a finding event and a delivered message are not always one-to-one.

Ground rules can independently disable channel or direct messages. See [Ways of Working](https://docs.nullify.ai/configuration/configuration-manager.md), [Slack delivery](https://docs.nullify.ai/connectors/slack/slack-notifications.md), and [Microsoft Teams](https://docs.nullify.ai/connectors/microsoft-teams.md). Investigate the finding's activity and delivery state before recreating a ticket or re-running a scan to force a notification.
