> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/iam-risk-analyzer/findings/findings-daily-alert-with-balkanid-slackbot.md).
# Findings (Daily Alert) with BalkanID Slackbot
BalkanID Risk Managers can get daily alerts for [Findings](/iam-risk-analyzer/findings.md) via the BalkanID Slackbot, keeping them up to date on the access issues that should be addressed without needing to visit the app (contact `support@balkan.id` to enable this alert).
## Daily Alerts
For each [Finding Rule](/iam-risk-analyzer/findings/setup-finding-rules-using-entity-filters.md) that has any findings, an alert will be sent via BalkanID Slackbot to each Risk Manager at 9AM CT every day.
Each such alert message includes the name and severity of the Finding, a summary of number of employees, identities and app integrations affected and a link back to the BalkanID web app for further information.
Additionally a list of matched Users and Identities is shown. See the screenshot below for a couple example alerts.
## Configuration
These alerts can be configured on the `Configure > System Notifications` page under `Findings`, where the alert can be toggled on and off for all and for individual Finding Rules. Additionally, the alerts for individual Finding Rules can be sent to Slack Channels instead of direct messages from BalkanID Slackbot.
### Enable/Disable
Findings (Daily alert) notifications can be disabled entirely with the notification group level toggle, and individually for specific Findings.
### Send to Slack Channels
The alerts for each Finding can be be sent to a Slack Channel instead of direct message using the `Send to Channel` option. `Default Channel` can be set as a fallback for Findings without a channel individually specified.
### Severity Level
If you'd rather not receive alerts for lower priority findings, but don't want to manage individually toggling specific Finding alerts on and off, you can set the `Severity Level` option, which is the minimum Finding Severity for which an alert will file. The default `Severity Level` is `High` to avoid noisy alerts, but it can be lowered or raised as needed.
### Rollup
To summarize and reduce notification noise further, multiple Findings can be combined with less details in a single alert, by setting the `Rollup` toggle for those Findings.
See [Notification Preferences](/getting-started/system-notifications-and-automatic-ticket-creation/notification-preferences.md) for more details on configuring notification preferences such as the `Allow user override` toggles.
---
# 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.balkan.id/iam-risk-analyzer/findings/findings-daily-alert-with-balkanid-slackbot.md?ask=&goal=
```
`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.