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

# Notifications

Tenant-level notification settings control how your tenant is alerted when StepSecurity threat intelligence flags a compromised component. Channels configured here apply tenant-wide, across every organization connected to the tenant.

For notification settings scoped to a single organization, including Harden-Runner detections, GitHub Checks results, and workflow run policies, see [Notifications](/workspace/settings/notifications.md) under Organization Settings.

### Accessing tenant notification settings

1. Open the StepSecurity dashboard and click **Back to Dashboard** if you are inside an organization view.
2. In the Admin console left menu, expand **Settings**.
3. Click **Notifications**.

<figure><img src="/files/lgro2May0vZ33vqtfeJQ" alt=""><figcaption></figcaption></figure>

### Notification Channels

These are the tenant-wide channels used for threat intel notifications. Configure one or more of the following:

| Field                 | Description                                                                                                                                                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Email**             | Email address that receives threat intel notifications.                                                                                                                                                                        |
| **Slack Webhook URL** | Slack incoming webhook, in the form `https://hooks.slack.com/services/...`. [Follow these instructions](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/) to create a Slack webhook.                 |
| **Teams Webhook URL** | Microsoft Teams incoming webhook. [Follow these instructions](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet) to create a Teams webhook. |

### Notification Events

Under **Notification Events**, select **Notify when StepSecurity threat intel flags a compromised component** to get notified about components flagged by StepSecurity threat intel.

Threat intel notifications cover the same incidents surfaced in the [Threat Center](/workspace/threat-center.md). Each incident identifies the compromised packages or Actions involved and the recommended remediation steps.

**Choosing threat intel notification granularity**

Once the event is enabled, open the **Threat intel notifications** dialog to choose when this tenant is notified:

<figure><img src="/files/x7ZQXdXvm4c5ERGYLoHY" alt=""><figcaption></figcaption></figure>

| Option                         | Behavior                                                                                            |
| ------------------------------ | --------------------------------------------------------------------------------------------------- |
| **All threat intel incidents** | Notify about every threat intel incident, whether or not this tenant is affected.                   |
| **Affected packages**          | Notify only when this tenant is affected by a compromised package, matched by name, at any version. |
| **Exact version only**         | Notify only when this tenant has the exact compromised version installed.                           |

Choose **All threat intel incidents** if your security team tracks ecosystem-wide threats regardless of exposure. Choose **Affected packages** or **Exact version only** to reduce alert volume to incidents that touch your own dependencies, with **Exact version only** producing the narrowest set of alerts.

Click **Done** to confirm your selection.

#### Saving your changes

Click **Save** to apply your channel and event configuration. Changes take effect for incidents raised after saving.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stepsecurity.io/administration/admin-console/settings/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.