> 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/enable-email-remediation.md).
# Enable Email Remediation
Now that you've configured [Material Detections](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-material-detections.md), [User Reporting](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md), [Email Provider Alerts](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-email-provider-alerts.md), and [Issue Triage](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-issue-triage.md), you're ready to enable remediation. Enabling **Email Threat Remediation** grants Material permission to take action on detected threats.
The recommended approach is a phased rollout: enable for a small trial group first, validate, then enable for your whole organization.
{% hint style="danger" %}
**Phishing simulations running? Update exempt IP addresses first.**
If you have phishing simulations running in any tool, [update your exempt IP addresses](/learn-more/risk-areas/email-threats/detect/issue-exemptions.md#set-defaults) before enabling to avoid false positives on your simulations.
{% endhint %}
### Enable for a trial group
Start with a small group, like your IT team or your own account, to confirm your configuration before rolling out org-wide.
1. As a super admin, log in to your Material instance.
2. From the toolbar, click **Explorer**.
3. Click **Groups** to enable for a group, or **Accounts** to enable for individual users.
4. Search for and open your trial group or account.
5. In the right panel, under **Custom Settings**, find **Email Threat Remediation**.
6. Set the value to **Custom**, then **On**.
After about a week, once you're satisfied with how remediation is behaving, proceed to enable globally.
### Enable remediation globally
1. As a super admin, log in to your Material instance.
2. From the toolbar, click **Settings** .
3. From the left navigation, click **Default Account Settings**.
4. Toggle **Email Threats** to **On**.
Once enabled, Material remediates both newly detected threats and any issues identified before enablement.
(To disable Email Threat Protection: in step 4, toggle to **Off**.)
### Manage remediation by group or user
After enabling globally, you can override the setting for specific groups or users. In **Explorer**, open the group or account, then under **Custom Settings**, set **Email Threat Remediation** to **Custom**, then **Off**. Select **Inherit** to restore the global setting.
***
## Enable Email Bomb Protection
Optionally, enable Email Bomb Protection at this point. Material automatically detects [email bomb attacks](#user-content-fn-1)[^1] and remediates to restore inbox availability. You can choose to detect only, auto-remediate (enable), or do nothing (disabled). [Learn more here](/learn-more/risk-areas/email-threats/detect/material-email-threat-detections/email-bomb-protection.md).
***
You can return to the Email Threat settings at any time to edit your response defaults and choices.
{% hint style="success" %}
Email Security is now deployed! Next, enable [File Security](/getting-started/deployment-guides/your-first-30-days/7-enable-file-security.md).
{% endhint %}
[^1]: an attack method that involves sending a large volume of emails within a short period, with the goal of overwhelming the receiver's inbox and potentially obscuring legitimate emails
---
# 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/enable-email-remediation.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.