---
title: "Configuring alert definitions"
canonical: "https://docs.devo.com/space/latest/95127055/Configuring%20alert%20definitions"
format: markdown
---
> Macro (toc)

## How are alerts sent?

Once you've created an alert, it will be automatically associated with your domain's default *sending policy*. This policy is partly defined by the *delivery methods* and the *anti-flooding policy* associated. 

![image](media://9db6ae56-f440-4222-911a-cd57926bd3d0)

The ***sending policy*** dictates how to send an alert, to whom, when, and how often. When the domain is created, there is a default sending policy that uses the e-mail address of the domain's creator as the recipient. This policy will distribute the alert by e-mail, to the domain owner, at any hour, all while respecting the default anti-flooding policy.  
You will want to set up new sending policies to accommodate your organization's needs but there must always be a sending policy marked as the default policy, which will be automatically assigned to newly-created alerts. You can also create new delivery methods and anti-flooding policies to associate to your sending policies:

- The ***delivery method*** dictates how an alert is sent and to whom. For example, a delivery method might be created to send an email to *[itsystems@yourcompany.com](mailto:itsystems@yourcompany.com)* or to distribute the alert message via Pushover to mobile device users.
- The ***anti-flooding policy*** limits the number of alerts to distribute in the event that the alert is triggered frequently over a short period of time. This way, the anti-flooding policy associated with a sending policy determines how often the alert message will be distributed.

## What tasks do I need to perform?

The following articles describe all you need to know about the tasks to configure defined alerts so that they reach the adequate recipient through the adequate channel.

> Macro (children)