# Managing alerts

In the application, there are configurable alert events that can be used to notify end users of various states including when a site is either powered up or powered down.

Alerts are configured on a organisationor departmental level, and are applied at the application level, this means one alert rule can be shared by multiple applications in your project, but at the time of writing, alerts can not be shared between projects.

### What types of alerts are there?

We currently have two types of alerts available:

* Power Up (when an environment is powered on)
* Power Down  (when an environment is powered off)
* Resource Terminated (when a resource no longer exists in the provider)
* Provider Conifg Error (when we can't connnect to the provider)&#x20;

When an alert is configured, it is configured to a specific event which gives you the flexibility to only alert certain users when a site is powered up i.e. your end client, or when a site is powered down i.e. your internal DevOps team who may have scheduled patching during the time it's powered down.

### How are users alerted?

At the time of writing, there are several ways that a user can be alerted:

* Slack
* Email
* Webhooks (pending)
* Teams (pending)

### Can I create alerts for one application only?

Yes you can! Alert rules can be configured for multiple applications or a single application.

{% embed url="<https://youtu.be/YfoUrSAPRSg>" %}


---

# Agent Instructions: 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:

```
GET https://docs.turnitoff.ai/simple-management/managing-alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
