# Forward Email Notifications into Slack or Microsoft Teams

{% hint style="warning" %}
This page requires review - Work In Progress
{% endhint %}

Sealights sends essential notifications—like coverage status, build results, Proof of Testing reports, and alerts—via email. To improve team visibility and collaboration, you can forward these notifications directly into your **Slack** or **Microsoft Teams** channels.

This guide provides **step-by-step instructions** for both integrations and includes links to the official documentation for further reference.

***

### 🔧 Prerequisites

Before you begin, ensure you:

* Receive Sealights emails or can configure forwarding rules
* Have admin access (or permission) to configure Slack or Teams integrations
* (Optional) Use filtering rules to forward only relevant Sealights alerts

***

### 🟦 Forwarding Sealights Notifications to **Slack**

Slack offers a built-in feature that allows emails to be sent directly into a channel or conversation via a **custom email address**.

#### ✅ Setup Steps

1. **Generate the Slack Channel Email Address**
   * Go to your Slack workspace (desktop app or web)
   * Open the desired channel or DM
   * Click the channel/DM name at the top → **Integrations tab** → **Send emails to this conversation**
   * Click **Get email address**
   * Slack will generate a unique email like `xxxx@slack.email` and send it via Slackbot\
     📎 [Slack Docs – Send Emails to Slack](https://slack.com/help/articles/206819278-Send-emails-to-Slack)
2. **Customize Email Appearance (Optional)**
   * Still under Integrations, click **Customize Email Appearance**
   * Choose a display name (e.g., “Sealights Alerts”) and an icon or emoji for clarity\
     📎 Customize Slack Email App
3. **Set up Email Forwarding to Slack**
   * Add the generated email address as a recipient in:
     * Sealights configuration (if supported per user/project)
     * Or use a **mail rule** in Gmail/Outlook to forward Sealights notifications to this Slack email
4. **Optional: Manual Forwarding via Gmail or Outlook**
   * Install Slack for Gmail or Slack for Outlook
   * Open an email, click the Slack icon, choose the target channel, and send it directly
5. **Test It**
   * Trigger a Sealights build or event
   * Confirm that the message arrives in Slack with proper formatting

#### 🧠 Notes and Tips

* Channel email addresses can be restricted by workspace admins
* All forwarded emails will appear as messages in the selected channel
* Replies in Slack do not go back to the original sender
* Limitations: \~30MB for total content size (for manual Gmail/Outlook apps)

📚 **References**:

* [Slack: Send Emails to Slack](https://slack.com/help/articles/206819278-Send-emails-to-Slack)
* Slack Blog: Email Meets Slack
* Guide from Workshop

***

### 🟪 Forwarding Sealights Notifications to **Microsoft Teams**

Microsoft Teams supports direct delivery of emails into channels via **channel-specific email addresses**. You can forward Sealights alerts using this built-in capability.

#### ✅ Setup Steps

1. **Enable Email Integration (Admin)**
   * Go to Teams Admin Center → **Teams > Teams Settings > Email Integration**
   * Make sure **"Users can send emails to a channel email address"** is enabled
   * Optionally, define allowed sender domains\
     📎 Teams Admin Email Docs
2. **Get the Email Address for the Channel**
   * In Teams, click **… (More options)** next to the channel name
   * Select **Get email address**
   * Copy the generated address (e.g., `yourchannel@teams.ms`)
3. **Forward Emails to the Channel**
   * Add this email to the Sealights recipient list
   * Alternatively, use your email system (Exchange, Gmail, etc.) to set a forwarding rule for Sealights emails
4. **Behavior of Incoming Emails**
   * The email will appear as a **post in the channel’s Posts tab**
   * **Attachments** are stored in SharePoint under the channel’s **Files > EmailMessages** folder
   * These folders only appear when attachments are included\
     📎 Microsoft Support – Send Email to Teams Channel
5. **Test It**
   * Send or forward a Sealights email to the Teams address
   * Ensure it appears correctly and attachments (if any) are saved in the Files tab

#### 🧠 Notes and Tips

* Only **channel members** can access attachments via SharePoint
* **Replies** in Teams will not reach the original email sender
* You may need IT help to create a **filtering alias** for only Sealights traffic (e.g., `sealights-alerts@yourcompany.com`)

📚 **References**:

* [Woshub – Send Emails to Teams Channels](https://woshub.com/send-email-teams-channel/)
* Microsoft Learn – Email to Teams
* Microsoft Q\&A: Attachments & Email Behavior

***

### ✅ Summary Table

| Platform           | Method                                 | Notes                                                  |
| ------------------ | -------------------------------------- | ------------------------------------------------------ |
| **Slack**          | Direct email address per channel       | Custom icon/label, appears as Slack post, simple setup |
| **Slack (Manual)** | Gmail or Outlook Add-On                | User-triggered, size limits, useful for one-off shares |
| **Teams**          | Direct email address per channel       | Appears in Posts tab, attachments stored in Files      |
| **Teams (Alt.)**   | Power Automate or mail rule forwarding | Optional for advanced scenarios or routing/filtering   |


---

# 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.sealights.io/knowledgebase/setup-and-configuration/sealights-email-notifications/forward-email-notifications-into-slack-or-microsoft-teams.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.