Threats is ready as soon as your company is on the LibraCyber console: there’s nothing to activate. Setting it up means choosing how your users report suspicious emails, installing the chosen report buttons, deciding what Threats does with each report, and verifying everything with a test report. In the end, every email reported by your users appears in Threats › Threats, your admins get a notification, and the reporting user receives your response.
Who should set it up?
A LibraCyber console admin whose role includes the Threats permission. On Microsoft 365, work together with a Global Administrator for your tenant, who deploys the report button and, if you choose, connects the Microsoft Report button. On Google Workspace, work with a Google Workspace admin who installs the LibraCyber Gmail add-on.
How long does it take?
Forwarding works immediately. After deployment, the LibraCyber Outlook add-in can take up to 72 hours to appear in users’ Outlook; it often shows up in Outlook on the web within minutes. The LibraCyber Gmail add-on can take up to 24 hours to reach all users. Plan your test report (Step 7: Verify it works) when the button is available. Optional integrations with Microsoft Defender (Step 6: Microsoft Defender and your tools (optional)) take longer: sending is available on request, and sender blocking can take up to 2 hours to verify.
What are the steps?
- Forwarding to
report@app.mantra.ms: all mail platforms, nothing to install. - The LibraCyber report button: Outlook add-in on Microsoft 365, Gmail add-on on Google Workspace.
- The Microsoft Report button: Microsoft 365, optional.
- Reporting from Smart Banners and banner alerts: if you use Smart Banners.
- Choose your settings.
- Microsoft Defender and your tools: optional.
- Verify it works.
Microsoft 365: steps 1–7, choosing which buttons you want in steps 2 and 3. Google Workspace: steps 1, 2 (Gmail add-on), 4, 5, and 7; your users report with the Gmail add-on, by forwarding, and from banners if you use Smart Banners.
Then: Deploy to users, Deactivation and offboarding, and Troubleshooting setup.
Prerequisites
You need an admin role with the Threats permission, your users registered in your company’s LibraCyber account, and, on Microsoft 365, a Global Administrator for the report buttons. Threats is available for your company by default.
| Requirement | Why it’s needed | How to check |
|---|---|---|
| Threats available for your company | It’s available by default. If it’s been disabled for your company, reports aren’t saved and nothing appears in Threats | The test report from Step 7: Verify it works appears in Threats › Threats |
| An admin role in the console that includes the Threats permission | Every item in the Threats menu and the content of every reported email require this permission | The Threats menu is visible. Roles and their permissions are set in General Settings › Admins |
| Your users registered in your company’s LibraCyber account | Only registered addresses can report. A report from any other address, like a personal mailbox or alias, is ignored with no message | Your users are listed in General Settings › User management |
| Microsoft 365: a Global Administrator for your tenant | Deploying the add-in means accepting its permissions for the whole tenant; connecting the Microsoft Report button changes Microsoft Defender and Exchange settings | The person can access the Microsoft 365 admin center and Microsoft Defender portal as a Global Administrator |
| Google Workspace: an admin who can install Google Workspace Marketplace apps for your organization | Installing the Gmail add-on for your users is an admin action in Google Workspace | The person sees Admin install on the add-on’s Marketplace page |
| Reports can leave your organization by email | Forwards to report@app.mantra.ms and copies your report mailbox sends to report-hook@app.mantra.ms must not be blocked by outbound filters or data loss prevention rules |
Test reports from Step 7: Verify it works are delivered |
| Optional: Smart Banners | Needed for the Report email button in banners and the Banner alerts tab | The Smart Banners menu shows the console, not a presentation page |
Which mail platforms and apps are supported?
Microsoft 365 and Google Workspace. Forwarding works from any mail app and any mail system, including on-premises Exchange and other providers, as long as the forwarding address is registered.
- Microsoft 365: forwarding, LibraCyber Outlook add-in, Microsoft Report button, and banner button with Smart Banners.
- Google Workspace: forwarding, LibraCyber Gmail add-on, and banner button with Smart Banners.
- Other mail systems (on-premises Exchange, HCL Notes, Bluemind, and others): forwarding only. The add-in and Microsoft button require mailboxes in Exchange Online.
- The add-in works in classic Outlook for Windows (recent Microsoft 365 versions), the new Outlook, Outlook for Mac, Outlook on the web, and Outlook for iPhone and Android. Outlook versions that are too old, like some installations of Outlook 2016 and 2019, show Outlook version not supported and suggest forwarding the email.
Does Threats require another product?
No: Threats is available for your company by default, no matter which product you use. Some features require another product. The Report email button in banners and the Banner alerts tab require Smart Banners. Integrations with Microsoft Defender require Microsoft 365.
Threats › Dashboard shows your company’s data only with the Email Security (ESG) product, while global data is always shown.
Setup steps
Start by choosing how your users will report (below), then follow the steps you’ve chosen, in order. Each step explains how to verify and how to undo it.
Which ways to report should we offer?
Forwarding always works. On Microsoft 365, add the LibraCyber add-in, the Microsoft Report button, or both; on Google Workspace, add the LibraCyber Gmail add-on; with Smart Banners, users can also report from the banner. Each method sends the entire email to Threats and is attributed to the reporting user.
| Reporting method | Mail platform | What you set up | What the user sees |
|---|---|---|---|
Forward to report@app.mantra.ms
|
All | Nothing: inform your users (Step 1: Forward to report@app.mantra.ms) | A confirmation email |
| LibraCyber Outlook add-in, Report phishing to LibraCyber | Microsoft 365 | Deploy the add-in (Step 2: LibraCyber report button) | A panel in Outlook confirms the report; the email stays in the inbox |
| LibraCyber Gmail add-on | Google Workspace | Install the add-on (Step 2: LibraCyber report button › B · LibraCyber Gmail add-on (Google Workspace)) | The add-on confirms the report in Gmail |
| Microsoft Report button, Report phishing | Microsoft 365 | A report mailbox that forwards to report-hook@app.mantra.ms (Step 3: Microsoft Report button) |
Microsoft’s confirmation, then a confirmation email; Microsoft removes the email from the inbox |
| Report email in a banner | Microsoft 365 and Google Workspace, with Smart Banners | Enabled by default (Step 4: Smart Banners: Report email button and banner alerts) | A browser page confirms the report |
What users see in each case, in detail: Report a suspicious email › Which reporting method works in my mail app?.
Can we offer several ways at once?
Yes. Reporting the same email twice in the same way creates only one report in Threats; reporting it in two different ways, for example by forwarding and with a button, can create two. If you deploy the LibraCyber add-in, users will see two report buttons in Outlook unless you hide the Microsoft one: in the Microsoft Defender portal, under User reported settings, choose Use a non-Microsoft add-in button. Or, connect the Microsoft button as well (Step 3: Microsoft Report button), so both go to Threats.
What’s the difference between the two addresses?
report@app.mantra.ms is for users who forward an email manually. report-hook@app.mantra.ms is for tools that send the reported email as an attachment: the Microsoft Report button via your report mailbox, the add-in when it can’t report directly, and report buttons from other vendors. Each address works only for its intended use.
Can we keep our current report button from another vendor?
Only if it sends the reported email as an attachment, from the reporting user’s address, to report-hook@app.mantra.ms. LibraCyber does not integrate with other vendors’ report buttons. Test it with a phishing simulation and a regular email before relying on it: the simulation should count as reported and the regular email should appear in Threats.
Can reports go to our own security mailbox first?
Yes, with the Microsoft Report button: your report mailbox keeps every report and forwards a copy to LibraCyber (Step 3: Microsoft Report button). Don’t manually forward reports from an internal mailbox to report@app.mantra.ms: the report would be attributed to that mailbox, not the employee, and Threats might not recognize the original sender.
Follow the steps in order: each has its own article.