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

# 🔔 Notifications & Alerts

LockThreat can notify you and your team in four ways: the in-app bell, email, Slack/Microsoft Teams, and custom webhooks — configured by an administrator in **Settings > Notifications & Alerts**.

## 13.1 How to configure it

**Settings > Notifications & Alerts > Integrations tab:**

| **Channel**          | **What's needed**                                                                            |
| -------------------- | -------------------------------------------------------------------------------------------- |
| Email (SMTP)         | SMTP Host, Port, optional Username/Password, Security (TLS/SSL/STARTTLS), From Email         |
| Slack                | Webhook URL, Channel (for example `#alerts`), a display Username                             |
| Microsoft Teams      | Webhook URL, Alert Title                                                                     |
| Custom API / Webhook | URL, HTTP Method, optional custom headers (JSON), Authentication (none/basic/bearer/API key) |

Each integration has a **Test** button to confirm the connection before relying on it.

**Alert categories** (each with its own tab): Framework alerts, Compliance alerts, Policy alerts, Firewall alerts, and Project alerts. For each category you can set score thresholds, choose which events notify you (for example creation, deletion, threshold breach), pick delivery channels, and manage the recipient list.

## 13.2 Errors you might see and how to fix them

| **Message**                                                        | **What it means**                                                                       | **What to do**                                                                   |
| ------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| A channel shows **Not Configured**                                 | Required fields for that channel are incomplete                                         | Fill in every required field for that channel and save                           |
| Test button shows a failure (for example an SMTP connection error) | The channel's credentials or URL are wrong, or the destination is unreachable           | Re-check the host/URL/credentials and test again                                 |
| You're not receiving expected alerts                               | The event type isn't enabled for that category, or your role doesn't show notifications | Check the relevant alert category's toggles, and confirm with your administrator |

## 13.3 What success looks like

Email (SMTP): ✓ Configured\
Slack: ✓ Webhook URL active

Microsoft Teams: ✓ Webhook URL active

Test result: ✓ Email test sent to <security@company.com>

Thresholds and recipients show as chips you can review at a glance, for example NIST 75%, Global 85%, with recipients like <security@company.com> ✕.

The bell icon shows unread counts in real time; use **Search** in the top bar to quickly jump to a connector, policy, project or setting.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.threatreaper.ai/user-guide/notifications-and-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.