> 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/configure-material-detections.md).
# Configure Material Detections
Material Detections are on by default, detecting malicious messages and creating issues for you to investigate. However, no response is enabled just yet.
The available response options are the same across Material Detections, User Reporting, Custom Detections, and Email Provider alerts, but defaults are configured separately for each detection type allowing you more custom control.
**For deployment**, we recommend you enable the default responses:
1. From the left navigation, navigate to **Email Threats** > **Settings** > **Material Detection**.
2. Under **Response**, choose **Remediate Messages**.
### Response Types
#### Banner
Banners appear on the top of a suspicious email.
The default text is "This message was identified as potentially suspicious" to give your users a moment to pause before they take any action on it, but you can update it as needed.
#### Block
Blocks disable access to links or attachments entirely. You also have the option to just require the user to confirm they trust the sender when accessing a link or attachment (known as a speedbump). For deployment, we recommend you begin with the block then update as needed.
#### Move Message to Spam
In addition to adding a banner and blocking link or attachments, the default response is to move Material Detected malicious messages to spam.
{% hint style="success" %}
We recommend you begin with these default responses so Material can take action right away. To learn more about customizing remediations, review [Settings](/email-protections/email-threats/settings.md).
{% endhint %}
### Next Steps
Now that you've enabled remediation for Material Detections, you need to also enable it for [User Reporting](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md) and Email Provider Alerts.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.material.security/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-material-detections.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
