> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/set-up-a-notification.md).
# Set up a notification
Notifications help your admins stay on top of what's going on in your workspace. You can create notifications via event subscriptions and have these alerts sent to Slack channels, emails, or other locations via webhook.
{% hint style="success" %}
**Optional, configure your Slack integration first.**
If you want notifications to go to Slack, [follow these directions](/integrations/integration-fundamentals/messaging-and-ticketing-integrations.md) to connect first then return to this guide to continue.
{% endhint %}
***
## Create a notification
For deployment, we recommend you begin with a notification alerting you if a user clicks through a [speedbump](https://docs.material.security/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/pages/9AAU4Kq3x2QYfnef1C10#id-3.-remediation-and-response).
Notifications are created in event subscriptions.
1. From **Integrations** (the puzzle icon in the top toolbar), click **API** > **Events.**
2. Click **Create Event**; the new event subscription form loads.
Slack
{% hint style="warning" %}
If you want notifications to go to Slack, [follow these directions](/integrations/integration-fundamentals/messaging-and-ticketing-integrations.md) to connect to Slack first.
{% endhint %}
In the Event Workflow:
1. Set the **IF** parameter to `Issue Change` . (Most event subscriptions will use `Issue Change` or `Issue Update`).
2. From the **Detections** list, search for then select `Account clicked through speedbump on a phishing message`.
3. In the **THEN** parameter, choose **Slack.**
4. Choose the Slack channel to send this notification to.
5. The default message includes a variable that displays the issue number in your notification.
6. From the **Properties to Include** drop down, include any properties you want displayed in your notification. Another useful parameter to include is `account.acctEmail` so you know which user clicked through the speedbump.
7. Optionally, add a **Button** to your notification. If you'd like a button to open the related issue, use the URL: `${issue.issueLink}`
8. Click **Send Test Event**. You should see something like this in the Slack channel you chose:
9. **Save**, then toggle the event subscription **On**.
Email
In the Event Workflow:
1. Set the **IF** parameter to `Issue Change` . (Most event subscriptions will use `Issue Change` or `Issue Update`).
2. From the **Detections** list, search for then select `Account clicked through speedbump on a phishing message`.
3. In the **THEN** parameter, choose **Email.**
4. Enter one or more recipient email addresses in the *To* field. You can separate multiple addresses using commas.
5. In the subject line, you can also include a variable like the time or message ID.
6. In the Body, consider something concise like `${caseMsgInteracted.interactedBy.actor.acctEmail} bypassed the warning on a remediated message.` You can also choose variables from the **Body** drop down.
7. Click **Send Test Event**. You should see something like this in the inbox you chose:
8. **Save**, then toggle the event subscription **On**.
Webhook
In the event workflow:
1. Set the **IF** parameter to `Issue Change` . (Most event subscriptions will use `Issue Change` or `Issue Update`).
2. From the **Detections** list, search for then select `Account clicked through speedbump on a phishing message`.
3. In the **THEN** parameter, choose **Webhook.**
4. In the method, choose **Post**.
5. Enter the URI from your webhook location/provider.
6. In Headers include the parameters you want to send., a quick way to create the content is to:
1. Choose **Slack** and configure it with everything you need.
2. Click **Advanced Mode**.
3. Copy the content.
4. Choose **Webhook** again.
5. Paste the content into the headers.
7. Click **Send Test Event**. Confirm your webhook is successful.
8. **Save**, then toggle the event subscription **On**.
{% hint style="info" %}
To send a notification to multiple channels, you need to create an event subscription for each.
{% endhint %}
---
# 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.material.security/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/set-up-a-notification.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.