> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/notifications.md). # Notifications ## Overview Notifications help your team stay informed without checking Birdie constantly. Use notifications to send the right updates to Slack or email channels, depending on the feature and channel you configure. Birdie supports two main notification types: * **Digests** for scheduled summaries * **Alerts** for threshold-based updates Before you create either one, set up a delivery destination in [Channels](/admin-and-settings/notifications/channels.md). ## Digests Digests send recurring summaries of feedback activity to Slack. Use them to share trends, reviews, or filtered feedback with a team on a fixed schedule. You choose the layout, filters, timing, and destination channels. Digests work well for regular reporting and team check-ins. See [Digests](/admin-and-settings/notifications/digests.md). ## Alerts Alerts notify you when a metric goes above or below a value you define. Use them to track important changes that need faster visibility, such as spikes, drops, or unusual movement in key metrics. You choose the metric, condition, timeframe, frequency, and delivery channel. Alerts work well for active monitoring and quick response. See [Alerts](/admin-and-settings/notifications/alerts.md). ## Choosing the right notification * Use **Digests** for recurring summaries. * Use **Alerts** for immediate signal on metric changes. * Use **Channels** to control where notifications are delivered. --- # 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://ask.birdie.ai/admin-and-settings/notifications.md?ask=&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.