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

User Reporting Methods

One of the most valuable ways to detect and remediate phishing emails is to have your employees report suspected messages for you to evaluate. Material places messages similar to each other in an issue, but how you respond to a user reported message is important. It gives you opportunity to reinforce this action, educate your users in addition to remediating in bulk rather than having to go one by one.

In addition to response defaults, specify your remediation defaults to automate your strategy.

Issue grouping across detection sources

Material deduplicates across all detection sources. If one of your users reports a message that Material has already flagged, or if Material later detects a message your users already reported, a single issue is created, not two separate issues.

The issue is filed under whichever detection source triggered first. Your users who reported the message still receive any configured reporter acknowledgments, regardless of which source created the issue.

To begin, from the left navigation expand User Reports, then click Settings. The reporting methods are under Reporting Methods.

User Reports > Settings

Forwarding

To streamline processing and support user awareness and training, you can include a specific email to forward user reported messages to. This is called a Reporting Address.

  1. Toggle the option on to enable forwarding, then enter any email addresses in the Reporting Addresses field. Separate multiple addresses with commas, for example email1, email2

  2. Click Save.

  3. If you're leveraging the Outlook "report phishing" button, also update your Microsoft Settings with the details described here.

Include a Forwarding Address

Intermediary Address

Sometimes reporting users forward emails to the wrong email by mistake. Include an intermediary address to ensure these emails get to the correct address.

To use intermediary addresses, toggle the option on, then separate with commas same as reporting addresses above.

Intermediary Address

Label

Make it even simpler for your users to report a suspicious message by allowing them to apply a Gmail label or Outlook category.

Toggle the Label option to On.

Label setting
User Reports > Settings
  • Note, the label name is Suspicious, and that is not changeable.

  • If a user applies the label and also forwards the email, only one issue is created or similar message added; we deduplicate repeated reports about the same message.

Email Provider UI (User Interface)

Email Service Providers (ESPs) often have a built-in mechanism for reporting email threats, usually a button. You can leverage this function to detect messages in Material as well. Check the box next to your ESP(s) to enable.

To learn more about Gmail phishing reporting functionality, review Google's Workspace Admin guides.

Email Provider UI
User Reports > Settings

Even if Email Threat Protection is disabled for a specific user or group, we still ingest any email they report using the methods above.

Outlook

To avoid issue creation delay when users click the "report phishing button" in Outlook:

  1. Set up a Reporting Address.

  2. Once you have the Reporting address designated, as a Microsoft admin navigate to https://security.microsoft.com/securitysettings/userSubmission and update the settings to send to that reporting mailbox in addition to Microsoft:

To learn more about Outlook phishing reporting, review Outlook's guides.


Identify who reported the message

  1. From the left navigation, expand User Reports, then click Issues.

  2. Open an issue.

  3. The Detected By field displays the user who reported the message. Scroll down to the bottom and hover over their name to view the report method. Click the user name to view more details about their account and related issues.

View User Reports

You can also search messages by user in the Explorer.

Last updated

Was this helpful?