> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/notifications.md).

# Notifications

Choose which Konvu summaries your team receives by email and in Slack.

Konvu sends two recurring summaries so your team hears about new risk without opening the dashboard. Manage both in **Organization Settings > Notifications**.

| Notification                                                                                                         | Email         | Slack                       | Default                  |
| -------------------------------------------------------------------------------------------------------------------- | ------------- | --------------------------- | ------------------------ |
| [**Weekly digest**](/konvu/triage-and-remediation/monitor-and-deliver/notifications/weekly-email-digest.md)          | Every Tuesday | Not available               | On for new organizations |
| [**Daily exploitable recap**](/konvu/triage-and-remediation/monitor-and-deliver/notifications/slack-daily-digest.md) | Not available | Every day, 11:00 AM Eastern | Off                      |

Combinations Konvu does not support yet appear as disabled switches.

## Who receives them

* **Email** goes to every active member of your organization with a verified email address, including members who sign in through SSO. To change who receives it, manage your members in **Organization Settings > Team**.
* **Slack** posts to the channel saved on your Slack integration. See [Slack Daily Digest](/konvu/triage-and-remediation/monitor-and-deliver/notifications/slack-daily-digest.md#connect-slack).

Notification settings apply to the whole organization. Any signed-in member can change them.

## Notifications versus data forwarding

Notifications summarize activity for people. [Data forwarding](/konvu/triage-and-remediation/monitor-and-deliver/data-forwarding.md) writes assessments onto findings in other tools, such as ArmorCode or Wiz. The two are configured separately, and turning one on never turns on the other.


---

# 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://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/notifications.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.