> For the complete documentation index, see [llms.txt](https://docs.tensorwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorwave.com/observability/notifications-and-alerts.md).
# Notifications & Alerts
TensorWave supports notifications via **Slack** and **Email** to help you stay on top of your infrastructure without having to watch a dashboard. Whether it's a storage threshold being crossed or an unexpected node reboot, alerts are designed to surface problems early — before they impact your workloads.
Alerts are built around cluster and node observability, giving your team visibility into the health of your infrastructure in real time. Slack alerts are configured at the organization level by admins, while email alerts are configured individually by each user.
***
### Slack Alerts
Slack alerts are organization-wide and can only be managed by org admins. When enabled, qualifying events are sent to your organization's connected Slack workspace.
#### Enabling Slack Alerts
Toggle **Enable Slack alerts** on to activate notifications. Use the workspace dropdown to select which Slack workspace should receive alerts.
#### Alert types
You can enable or disable individual alert types depending on what's relevant to your organization. These include events such as low storage on nodes, low shared storage, and node reboots, among others.
***
### Email Alerts
Email alerts are per-user. Each team member independently controls which notifications are delivered to their account email address.
#### Enabling Email Alerts
Toggle **Enable email alerts** on to activate notifications. Alerts are sent to the email address on your profile. To update this address, go to **Profile** settings.
#### Alert types
The same set of alert types is available for email as for Slack. Each can be toggled on or off independently based on your preferences.
***
### General Notes
* Only org admins can enable or modify Slack alerts.
* Slack and email alerts are independent and can be enabled in any combination.
* Individual alert types can be toggled without disabling alerts entirely.
* Alert thresholds are set to TensorWave's recommended defaults.
---
# 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.tensorwave.com/observability/notifications-and-alerts.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.
