Security

Problem When a teammate reports a conversation as phishing or spam, there is no way to forward that signal to the organization's security tools (SIEM, SOC inbox, or third-party providers). Request When phishing/spam is reported, deliver a notifica...

Problem Front does not support Microsoft 365 sensitivity labels (Purview), so teams cannot set, view, or change labels that enforce encryption and watermarking protections on emails. Request Add support for viewing and applying M365 sensitivity la...

Problem Front lacks automated tools to help teams identify phishing emails, especially as AI-generated phishing attempts become more sophisticated. Request Provide phishing detection capabilities such as rule actions triggered by first-contact ema...

Problem Admins cannot selectively disable specific actions like contact field editing or message replies. Edits to contact fields in Front do not sync back to CRMs, causing data quality issues. There is also no way to dynamically restrict actions ...

Problem Emails sent or received using O365's native encryption cannot be decrypted and viewed within Front, forcing teammates to switch to Outlook. Request Allow O365/Azure encrypted messages to be decrypted and read in Front, and enable sending e...

Problem ProofPoint's Report Phish extension is integrated in Microsoft 365, but using it with Front requires downloading the email and opening it in Outlook, creating friction for users. Request Integrate ProofPoint Report Phish extension support ...

Problem The "Report Phishing" button only reports to Front's team, not to the organization's internal security team. Organizations with their own phishing response process cannot redirect or disable this functionality. Request Allow admins to disa...

Problem Front's DKIM configuration is limited to 1024-bit keys, which are increasingly considered insufficient by security standards such as NIST recommendations. Request Add support for 2048-bit DKIM keys, aligning with current security best prac...

Problem The API returns both trash-deleted and spam-deleted emails with the same "deleted" status, making it impossible to distinguish user-deleted emails from automatically-filtered emails. Request Expose separate status indicators in the API to ...

Problem There is no rule action to automatically classify messages as spam, limiting automated spam management capabilities. Request Add a "Send to Spam" action in the rules engine, so admins can automate spam handling based on rule conditions.