Currently, agents silently ignore emails from any sender not registered as a Hatz platform user in the tenant. This prevents agents from being triggered by external SaaS automation (e.g., scheduled reports from vendor platforms).

Requested: Allow workspace admins to whitelist specific external email addresses or domains that a particular agent can receive and process emails from.

Examples:

automation@extdomain.com (specific address)

*@extdomain.com (entire domain)

Safeguards: Allowlist-only (no "accept all external" wildcard), SPF/DKIM/DMARC validation recommended.

We built a VMaaS (Vulnerability Management as a Service) agent that:

Receives scheduled vulnerability scan reports from SaaS VM program (automation@extdomain.com)

Processes them into remediation workbooks

Emails technicians for QA review

Delivers the final package to the vCIO

Currently blocked at steps 1 and 3:

Step 1: ThreatMate's email is silently dropped (external sender)

Step 3: Agent's email to the technician is saved as a draft instead of sending

We've had to build workarounds with Power Automate and reply-to tricks, but these add complexity and points of failure that the agent was designed to eliminate.