For the complete documentation index, see llms.txt. This page is also available as Markdown.

Settings

Resolve issues after applying remediation

After you apply remediations, you can configure the issue resolve in the same flow. If you choose this option, any matching or similar messages will create new issues.

There are two ways to add this to an issue:

  1. Add Resolve issue after applying remediation to your default Email Threat responses:

  1. Update the response in an individual issue to include Resolve issue after applying remediation. This manually resolves the issue immediately.

Response for unreviewed messages with default remediation

Templates you apply here will send a reply to reporters as soon as they report a suspicious email before it's been classified (classification displays as none).

As soon as the case is classified, new reporters of the same message or a similar one will receive one of the messages defined below. Learn more in banner & template best practices.

The original reporter will not receive one of these other messages by default, but if you want them to receive subsequent messages after you classify a case, from the case detail reporter response check the option to Also send to previous reporters:

You choose the default response for each detection category. The chosen behavior applies to all issues in that detection category when the issue is created.

You can then analyze any issue and manually update the response specific to that issue if needed. For example, if a user reports a suspicious email that you want to add more context to, you can update your response message on the issue level and that will overwrite your more generic, default message that is created by default for all user reports.

Choose Default Responses

Response Types

For Material Detections, User Reporting, Custom Detections, and Email Provider alerts you can set these defaults:

Condition / Scenario
Preferred Action
When to Use It
Default for

High-confidence malicious (malware, phishing kit, known bad domain, spoofed internal)

Block

Threat is clear and severe; there is no legitimate need for the user to ever see or interact with the message.

Malicious

Suspicious but possibly legitimate (lookalike domain, odd request, gift card requests)

Speedbump

Risky but ambiguous; user business context may validate it. You want to slow them down and add friction, not fully block.

Unknown

Legitimate but misconfigured or unusual (partner using personal email, broken auth, strange but plausible)

Speedbump

You expect some legitimate traffic in this pattern but want users to double-check before acting.

Unknown

Clearly unwanted bulk or marketing (low-value promos, repeated cold outreach, obvious-but-harmless spam)

Move to Spam

Not harmful, just inbox noise. Let users still retrieve it from Spam if needed, but keep it out of the primary mailbox.

Malicious, Spam

Useless, confusing, or system noise (bounces, broken auto-replies, content-free messages to shared boxes)

Delete

No security threat and no business value. Removing it entirely reduces clutter and user confusion.

--

Known good / normal traffic

No Response

No meaningful risk indicators; user experience should remain uninterrupted.

Safe

Update Response Defaults

For Material Detection, User Reporting, Custom Detections, and Email Provider alerts you can set these defaults:

To begin, navigate to the settings for the defaults you want to set. For Material detections, from the left navigation expand Email Threats, expand Settings, then click Material Detection. For email provider alerts, click Email Provider Alerts instead. For user reporting, expand User Reports, then click Settings. Custom detection responses are set on each detection. Consider the use cases above, then review the following for more detail:

No Remediation

Issues are still created. Responses aren't applied, and the message will remain in your user's inbox with no modification. If you want your analysts to always triage issues before remediation, choose this option.

Add banner to email

Optionally, include a banner on the top of a suspicious email. Depending on the detection type, thank your user for reporting, include more information about next steps, etc. Learn more about banner creation and best practices here.

Delete associated calendar events

Material soft-deletes calendar events associated with the message. It does not move them to spam.

The invite disappears from both the organizer's and attendee's calendars. Material stores an encrypted ICS copy independently of the email provider. This copy supports restoration when the response changes.

This response acts on the message that carried the invitation. For invitations that arrive without a message, and the Google Workspace and Microsoft 365 settings that stop them, see calendar invite attacks.

How restoration works: Material extracts the ICS content from the original message and stores it in its own encrypted storage. During restoration, Material uses the calendar API to create a new calendar event from that stored ICS.

How to verify the behavior:

  1. Keep "Delete associated calendar events" disabled in the global rule settings.

  2. Send a test calendar invite from an external account to an enrolled test user.

  3. Create an issue from the message (Explorer > Messages, select the message, then click Create Issue).

  4. Manually add the remediation: On the issue detail page, enable "Delete associated calendar events".

  5. Verify deletion: Check the test user's calendar. The event should be removed.

  6. Test restoration: Reclassify the issue as "Safe" or remove the calendar deletion remediation.

  7. Verify restoration: Check the test user's calendar. The event should reappear as a new event.

Move message to spam

Messages go directly to the user's spam folder. Your user can still move them from spam back into their inbox. This response applies to messages from both business domain senders and freemail senders (like Gmail and Yahoo).

Including a banner is a good choice here so they can learn why this email was moved in the first place. Include specific language so they proceed with caution. Learn more about banner creation and best practices here.

Delete messages (and associated calendar events)

Messages and any associated calendar events are deleted and inaccessible to users.

By default, Material maintains the original message so updating an issue response from 'Delete' to something else will restore the message and calendar events. However, if Mailbox Mirroring is enabled, how long restoration is possible depends on your Mailbox Mirroring retention settings.

This response option can't be combined with other response types.

If a message is deleted in Material before it is assigned to an issue with this response, any associated calendar events will not be removed.

Resolve issues after applying remediation

After you apply remediations, you can configure the issue resolve in the same flow. If you choose this option, any matching or similar messages will create new issues.

There are two ways to add this to an issue:

  1. Add Resolve issue after applying remediation to your default Email Threat responses:

  1. Update the response in an individual issue to include Resolve issue after applying remediation. This manually resolves the issue immediately.


User Reporting Reporter Acknowledgements

Sending a follow-up message ensures users are informed of actions taken, reinforces security awareness, and confirms that their report was valued. It also provides guidance on any additional steps they should take, fostering a proactive security culture and improving response to future incidents.

To navigate to user reporting default settings, from the left navigation expand User Reports, then click Settings.

In the Reporter Acknowledgement settings, leverage templates to quickly and consistently respond. You can also use variables to further customize responses:

email
Reporter Acknowledgement

This is an example of a report acknowledgement, auto-sent in response to a user report:

Reporter Acknowledgement

If you don't write anything custom, we send the header/footer and base template.

Response for unreviewed messages with default remediation

Templates you apply here will send a reply to reporters as soon as they report a suspicious email before it's been classified (classification displays as none).

As soon as the case is classified, new reporters of the same message or a similar one will receive one of the messages defined below. Learn more in banner & template best practices.

The original reporter will not receive one of these other messages by default, but if you want them to receive subsequent messages after you classify a case, from the case detail reporter response check the option to Also send to previous reporters:

Response for exempt messages from a trusted sender

These responses are sent to for messages reported that come from a trusted sender you established in VIP Impersonation or in Issue Exemptions.

Response for messages marked safe

These responses are sent to anyone who reports a message that falls into an issue classified as safe in the issue detail view.

Response for messages marked malicious

These responses are sent to anyone who reports a message that falls into an issue classified as malicious in the issue detail view.

Response for messages marked spam

These responses are sent to anyone who reports a message that falls into an issue classified as spam in the issue detail view.


Currently deploying?

Click here to return to the Enable Email Threat Protection guide.

Last updated

Was this helpful?