> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/policies/anomaly-detection/create-anomaly-detection-policies.md).
# Create anomaly detection policies
Organization Managers can create new anomaly detection policies by defining the policy name and description, and the parameters under which anomalies will be identified.
FinOps for Cloud supports two types of anomaly detection policies, including **Resource count** and **Expense**. To learn about these policy types, see [Anomaly Detection](/policies/anomaly-detection.md).
### Creating a new anomaly detection policy
To create a new anomaly detection policy:
1. Navigate to the **Anomaly detection** page, then select **Add**. The **Create anomaly detection policy** page opens.
The Create anomaly detection policy page in FinOps for Cloud.
2. Enter a descriptive name for the policy and select the policy type:
* Select **Resource count** if you want the daily resource count to not exceed the average amount over the last evaluation period, according to the threshold percentage.
* Select **Expense** if you want FinOps for Cloud to detect when everyday expenses exceed the average sum for the last evaluation period above the threshold percentage.
3. Enter the evaluation period in days and define the threshold percentage.
4. (Optional) Select any filters to be used to trigger policy alerts. You can apply multiple filters. If applicable, select **Show more** to view all filter options.
5. Select **Save** to finish creating the new policy.
Once the policy has been created, FinOps for Cloud sends an email notification to the Organization Manager every time an anomaly is detected.
---
# 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.finops.softwareone.com/policies/anomaly-detection/create-anomaly-detection-policies.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.
