# Email

The Email integration sends Interlynk notifications directly to email addresses — individual inboxes, shared mailboxes, or distribution lists.

***

## Purpose

* Deliver vulnerability, policy, license, and upload notifications via email.
* Reach team members who may not have access to Slack or Teams.
* Send to shared mailboxes or distribution lists for team-wide visibility.

## Setup Steps

1. Navigate to **Settings > Organization > Integrations**.
2. Click **Email**.
3. Click **Add New** to add an email notification configuration.
4. Enter:
   * **Email Address**: The target email address.
   * **Notification Type**: Select the notification level (**All**, **Alert**, **Warning**, or **Info**).
   * **Frequency**: Currently supports **Instant** delivery.
5. Click **Save**.

You can add multiple email configurations to route notifications to different addresses with different severity filters.

## Organization Notifications

Email notifications at the organization level are delivered for events across all products and environments. Configure organization-wide defaults in **Settings > Organization > Notifications** to control which event types generate emails.

## Delivery Failures

If email delivery fails:

* Verify the email address is correct and the mailbox is active.
* Check your organization's spam/junk filters for messages from Interlynk.
* If using a distribution list, ensure external senders are allowed.
* Contact Interlynk support if delivery issues persist.

## DMARC/SPF Recommendations

To ensure Interlynk emails are not rejected or marked as spam by your mail server:

* **Allowlist** the Interlynk sending domain in your email gateway.
* If your organization enforces strict **DMARC** policies, add the Interlynk sending domain to your SPF record or configure an exception.
* Check your **quarantine/junk folder** if notifications are not arriving.

{% hint style="info" %}
Interlynk sends emails from its own mail infrastructure. Contact Interlynk support for the current sending domain and IP ranges if needed for allowlisting.
{% endhint %}

## Required Permissions

### Interlynk

| Permission           | Purpose                            |
| -------------------- | ---------------------------------- |
| `view_connections`   | View email integration settings    |
| `edit_connections`   | Add or update email configurations |
| `delete_connections` | Remove email configurations        |

## Security Notes

* Email addresses are encrypted at rest.
* Be cautious when adding external email addresses — notifications may contain vulnerability details.
* Use distribution lists or shared mailboxes instead of personal addresses for team notifications to avoid disruption when team members leave.

## Troubleshooting

| Issue                                | Cause                                    | Resolution                                              |
| ------------------------------------ | ---------------------------------------- | ------------------------------------------------------- |
| Emails not received                  | Address typo or mailbox full             | Verify the email address and mailbox status             |
| Emails in spam/junk                  | Sender not allowlisted                   | Add Interlynk sending domain to your allowlist          |
| Duplicate emails                     | Multiple email configs with same address | Remove duplicate entries in integration settings        |
| External distribution list rejecting | List does not accept external senders    | Update the distribution list to allow external messages |


---

# 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.interlynk.io/administration/email.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.