> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/flex-modes/save-and-share-your-work/use-alerts.md).

# Use alerts

Create alerts to track important values and get notified when they meet the conditions you set.

Alerts are a special type of favorite. You can use a dynamic period so an alert automatically moves forward over time as the underlying data updates.

Someone in your organization might share alerts with you, or you can create your own.

## View alerts

Alerts display on your homepage on the **All** and **Alerts** tabs. The alert's color indicates its current status, so you can quickly see whether the value is red, yellow, or green. Click an alert to open it and view the saved analysis point.

<div align="left"><figure><img src="broken://files/eWOCKaHg3XUeTzvRFSOk" alt="" width="319"><figcaption></figcaption></figure></div>

Depending on its delivery settings, you might also receive the alert by email.

## Create an alert

There are different contexts from which to create an alert. The steps are similar, but the starting points are different.

### Create an alert from an analysis point <a href="#alerts-createanalert" id="alerts-createanalert"></a>

1. Set up your grid the way you want.&#x20;
2. Click **Create alert** in the toolbar. This option is only available in a dimension view. The **Create alert** panel opens next to the grid.

   <figure><img src="broken://files/5w7KVZZcMPk5NVau7Dvv" alt=""><figcaption></figcaption></figure>
3. In the grid, select the column you want to create the alert on. By default, the **Total** column is selected, but you can select any value column, including a calculation column you've added to the grid.
4. In the **Create alert** panel, enter a name for the alert and, optionally, a description.
5. Select the metric used to calculate the value, such as **Sum**, **Average**, **Count**, **Max**, or **Min**.
6. Optional: Enter a prefix and suffix to display before or after the value and give it more context, such as a currency symbol.
7. Set the thresholds:
   * Select whether **Higher is better** or **Lower is better**. This determines the order of the red, yellow, and green statuses.
   * Enter the two values that define the thresholds between the three statuses.
8. Select when you want to be notified:

   * **Threshold crossed**: You're notified when the value moves from one status to another, for example, from green to yellow.
   * **Red**, **Yellow**, or **Green**: You're notified when the value is in the selected status.

   You can select multiple conditions. If you don't select a condition, you're notified every time the alert runs.
9. Optional: Under **Delivery method**, select **Email** if you also want to receive the alert by email.&#x20;
   * Alerts display on your homepage by default.
   * Email delivery works like a subscription. You can set your [subscription preferences](/basics/getting-started/subscriptions.md#configure-the-subscription) to control how the alert is delivered. If several alerts trigger at the same time, they're combined into one email and sorted from red to green, with descriptions included, so you can quickly see what needs your attention.
10. Optional: Click **Test** to test the alert.
11. Click **Create**.

### Create an alert from a favorite

Create an alert based on an analysis you've saved as a favorite.

1. Open the favorite and ensure you're in a dimension view.&#x20;
2. Click **Create alert** in the toolbar. The **Create alert** panel opens next to the grid.

   <figure><img src="broken://files/8KQOUkg0WAih8SjBgBJn" alt=""><figcaption></figcaption></figure>
3. Set up the alert as described in steps 3–11 in **Create an alert from an analysis point** above.

## Update an alert

1. Open the alert. The grid opens with the saved analysis point and the **Update alert** panel open.
2. Make your changes and click **Update**.

<div align="left"><figure><img src="broken://files/0ErcnyKDPI989kLtkm68" alt="" width="234"><figcaption></figcaption></figure></div>

## Subscribe to an alert

Subscribe to an alert to receive email notifications when the alert triggers.

When you create or update an alert, select **Email** under **Delivery method**. You can then set your subscription preferences, such as how the alert is delivered.

<div align="left"><figure><img src="broken://files/yhENiKjsBHrnevgWh0Yy" alt="" width="204"><figcaption></figcaption></figure></div>

## Delete an alert <a href="#alerts-deleteanalert" id="alerts-deleteanalert"></a>

1. Open the alert. The grid opens with the saved analysis point and the **Update alert** panel open.
2. Click **Create alert** in the toolbar, then click **Delete alert** > **Delete**.

<div align="left"><figure><img src="broken://files/8z5qgX1wXzBjrc02SLH4" alt="" width="226"><figcaption></figcaption></figure></div>


---

# 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.phocassoftware.com/flex-modes/save-and-share-your-work/use-alerts.md?ask=<question>&goal=<endgoal>
```

`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.
