> 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/learn-more/risk-areas/email-threats/detect.md).

# Detect

Through a combination of algorithms and human threat detection, Material does the bulk of the work for you in detecting suspicious emails, but there are like scenarios unique to your organization.

You have control over where malicious messages are sent, how you communicate with your employees about suspected phishing, messages that shouldn't create issues, etc.

{% hint style="info" %}
The pre-built, Material default settings are effective in most situations. Customization is meant to help you tweak as needed, and to align closely with your security strategy.
{% endhint %}

To account for your custom scenarios and issue creation preferences, configure default detection settings in these areas:

<table><thead><tr><th width="244">Detection Type</th><th>Options</th></tr></thead><tbody><tr><td><a href="/pages/jSk7bDsvN0anoWp3wrTc">Material Detections</a></td><td>No configuration needed, enabled by default</td></tr><tr><td><a href="/pages/ykAmqqf6D76AgdWBxi4f">User Reporting Methods</a></td><td>Choose how users report suspicious messages</td></tr><tr><td><a href="/pages/lmal7nTbzLdIIWdIUH6B">Email Provider Alerts</a></td><td>Choose which Gmail alerts you would like to ingest from the <a href="https://support.google.com/a/answer/9104586">Google Workspace Alert Center</a>.</td></tr><tr><td><a href="/pages/BbiduvArZdSnJJalKFPP">Custom Detections</a></td><td>If something isn't already covered in another detection, define your own criteria for flagging messages.</td></tr><tr><td><a href="/pages/ZsHRIhS0mh4TkooPEMvc">VIP Impersonation</a></td><td>Create known aliases, like a CEO or other frequently impersonated team member, and avoid triggering account protection erroneously</td></tr><tr><td><a href="/pages/ozcxVXkcpXTHCc1rHnyY">Trusted Entities</a></td><td>Prevent specific use cases from being added to issues after detection</td></tr></tbody></table>

{% hint style="success" %}
After you've determined your detection settings, review the default responses and remediations for each of these detection types to confirm you're happy with them.
{% endhint %}

***

## Navigate to Settings

Each of the above settings' individual details are described in the guides in this section. To navigate to the settings page in your app:

1. As an **admin**, **settings admin, or analyst:** log in to Material Security.
2. From the top toolbar, click the **cog** icon labeled **Settings.**
3. Click **Email Threats,** then navigate to the settings you need to edit either via the overview or in the left navigation.

{% hint style="warning" %}
Note: If your role is a Tenant level role, you can only update settings for your assigned tenant. Global roles can update Global settings. [Learn more here.](/learn-more/administration/admin-roles.md)
{% endhint %}

<figure><img src="/files/LLSTW1VoxpRYQYFQAMYG" alt="the cog icon represents settings"><figcaption><p>Email Threat Settings</p></figcaption></figure>


---

# 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/learn-more/risk-areas/email-threats/detect.md?ask=<question>&goal=<endgoal>
```

`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.
