> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anomalyarmor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email

> Send AnomalyArmor alerts to email addresses for team notifications

<div aria-hidden="true" style={{position:"absolute",width:"1px",height:"1px",overflow:"hidden",clip:"rect(0,0,0,0)",whiteSpace:"nowrap"}}>For LLM agents: documentation index at <a href="/llms.txt" tabIndex={-1}>/llms.txt</a>, full text at <a href="/llms-full.txt" tabIndex={-1}>/llms-full.txt</a>. Append .md to any page URL for plain markdown.</div>
Send AnomalyArmor alerts to individual email addresses or distribution lists. Email is ideal for alerts that don't require immediate action or for team members who prefer email over chat.

## Why Email?

Email works well for certain alert scenarios:

* **Digest-friendly**: Batch multiple alerts into summaries
* **Universal**: Everyone has email, no app installation needed
* **Async**: Good for non-urgent notifications
* **Auditable**: Built-in record of all alerts received

## Prerequisites

Before you begin:

* AnomalyArmor account with alert configuration permissions
* Valid email addresses for recipients

## Setup Guide

### Step 1: Navigate to Destinations

1. Log in to AnomalyArmor
2. Click **Alerts** in the left sidebar
3. Select **Destinations** tab
4. Click **Add Destination**

### Step 2: Select Email

From the destination type list, click **Email**.

### Step 3: Configure Recipients

Enter the email addresses that should receive alerts:

| Field                | Description                                      |
| -------------------- | ------------------------------------------------ |
| **Destination Name** | A descriptive name (e.g., "Data Team Email")     |
| **Recipients**       | Email addresses, one per line or comma-separated |

<Note>
  You can use distribution lists or group email addresses to reach multiple team members with a single destination.
</Note>

### Step 4: Test the Connection

Click **Send Test Alert** to verify delivery:

```
Test alert sent to: team@example.com
Subject: [AnomalyArmor] Test Alert
```

Check the recipient inbox (and spam folder) to confirm the message arrived.

### Step 5: Save

Click **Save** to complete the setup. Your email destination is now ready to use in alert rules.

## Alert Email Format

AnomalyArmor emails include:

* **Subject**: Alert type and affected asset
* **Body**: Full alert details with links to AnomalyArmor
* **Unsubscribe link**: Manage notification preferences

## Best Practices

### Use Distribution Lists

Instead of individual emails, use a team distribution list:

* Easier to manage team changes
* Single destination covers entire team
* Reduces configuration maintenance

### Pair with Other Destinations

Email works well alongside real-time channels:

| Alert Type       | Destinations              |
| ---------------- | ------------------------- |
| Breaking changes | Slack + PagerDuty + Email |
| Schema changes   | Slack + Email             |
| Informational    | Email only                |

### Avoid Alert Fatigue

Email alerts can pile up quickly. Consider:

* Routing only important alerts to email
* Using Slack for high-volume informational events
* Setting freshness SLAs with buffer (e.g., 2x expected update time)

## Troubleshooting

### Emails going to spam

**Cause**: Email filters flagging AnomalyArmor messages.

**Fix**:

1. Add `alerts@anomalyarmor.ai` to your allowlist
2. Mark test emails as "Not Spam"
3. Contact your IT team to allowlist the domain

### Emails not arriving

**Cause**: Invalid email address or delivery issues.

**Fix**:

1. Verify the email address is correct
2. Check spam/junk folders
3. Try a different email address to test
4. Use **Send Test Alert** to verify the destination

## Common Questions

### Can I send AnomalyArmor alerts to a distribution list?

Yes. Enter any group or distribution list address in the recipients field, the same as an individual mailbox. This is the recommended pattern, since managing membership in your mail system is easier than editing AnomalyArmor destinations when the team changes.

### Why are AnomalyArmor emails going to spam?

Alerts come from `alerts@anomalyarmor.ai`. Add that address to your allowlist, mark any test email as "Not Spam", and ask your IT team to allowlist the domain if the issue persists. Corporate spam filters are the most common cause of missing alerts.

### Can I add multiple recipients to one email destination?

Yes. Enter addresses one per line or comma-separated in the recipients field. Every alert sent to that destination is delivered to all listed addresses.

## Next Steps

<CardGroup cols={2}>
  <Card title="Alert Rules" icon="bell" href="/alerts/alert-rules">
    Create rules that route to email
  </Card>

  <Card title="Best Practices" icon="lightbulb" href="/alerts/best-practices">
    Reduce alert fatigue
  </Card>
</CardGroup>