Managed SAT

Feature Request: Dark Web Monitoring (SAT And/Or ITDR) Dark Web Monitoring is one of those services that sounds a bit cooler than it actually is—at its core, it’s just cross-referencing user emails against known breach databases and generating clean, actionable reports. But despite its simple mechanics, it’s still undeniably useful for client conversations and risk awareness. Right now, trying to run this at scale using piecemeal APIs and custom integrations across all our managed tenants is daunting, tedious, and hard to maintain. While Huntress SAT focuses on education/behavioral training and ITDR focuses on identity threat detection and response, bridging them with built-in Dark Web Monitoring would be a huge win. Running these reports against active learners or protected identities just makes sense: Competitive Parity: Competitors in the SAT space (KnowBe4, Avanan, Keepnet, Defendify, etc.) regularly bundle Dark Web Monitoring into their base SAT packages at similar price points. Immediate ITDR Impact: Including this inside ITDR’s Security Assessment feature would give MSPs instant, "Day 1" value to present to prospective or newly onboarded clients during initial assessments. Eliminating MSP Friction: Instead of MSPs stringing together third-party lookups, Huntress could centralize identity exposure reporting right where our identity management already lives. I don’t normally ask Huntress—who consistently stands out by avoiding industry fluff—to adopt something just because it’s a "norm." However, bringing native Dark Web reporting into SAT or ITDR would add incredible value to subscribed MSPs without forcing us to bolt on extra single-feature vendors.

There's currently no way to know when the "report a phish button" needs to be updated. The admin portal doesn't show a version number and there's no notification setting to be alerted when an update is available. Since it has to be manually updated in M365, there should be some way for us to know when we need to do that.

Add an option to set an end date relative to account enrollment date in the assignment. For example, setting an end date of 60 days after enrollment will result in: Initial members will have an end date of 60 days after creation of the assignment Learners enrolled later on will have 60 days starting from their enrollment date This would be particularly useful for a "New Learner" type of assignment. It will ensure the completion of their basic catch up training is tracked with Manager notifications without having to manually review progress every time.

Continual iterations on our gamification and leaderboard experiences.

We're looking for a feature in Huntress Managed SAT to send global notifications to admins when any user fails a phishing test. Currently, notifications can be sent to "managers" for their direct reports, but we need a way for our team to receive these alerts without adding ourselves as managers for each user or account. This would greatly simplify oversight for our clients who rely on us to help manage phishing tests. Has anyone found a workaround for centralized admin notifications, or is this on the roadmap?

We would like the ability to generate static, point-in-time reports that preserve data exactly as it existed when the report was created. Currently, reporting data for assignments and phishing campaigns updates dynamically as user records change, including learner status. For example, an employee who was active when an assignment was issued in December 2025 but resigned in February 2026 is now reflected as inactive when that same December 2025 report is viewed at a later date. This results in historical reports no longer accurately representing the population and learner statuses at the time of the campaign or assignment. For audit, compliance, and trend analysis purposes, we need the option to generate or export frozen historical reports that retain all user and assignment data as it existed on the report date, regardless of subsequent changes to employee status or other learner attributes. This would ensure the accuracy and integrity of historical reporting.

When a custom Phishing campaign is launched, the Learner count for the campaign is 0, until the phishing emails start sending. For a Scheduled campaign, this can be a few days or more, and it visually is confusing for Admins, who would expect to see the Learner count equal to what they chose for that test. Alternatively, it would be more consistent to show the total count of Learners set for that phishing assignment from the start of the campaign launch.

Support confirmed the only ways to set up the new "Manager Notifications" feature are to select Learners and manually enter the Manager's email address, or to configure the "manager" field in your synced provider (e.g.: Entra ID). If you don't have Entra synced, or don't want to use the synced provider's "manager" field value for this setting, it would be nice to have a default "Manager" setting in SAT so you don't have to either rely upon the upkeep of a synced provider's directory or manually enable it for each user - that would be tough to keep up with.

In Canada, the Official Languages Act (OLA) requires bilingual support (many provinces also have their own regulations, usually stricter, like Quebec and Ontario), so French audio (in addition to subtitles) would be required. As an MSP, we managed Crown corporations, so for us this is a hard requirement. Now there is a loophole, since the service has to be equivalent to its counterpart (english or french), having a version with ONLY subtitles (no English audio, tenant-wise), is acceptable.

When a user reports a phishing email create a ticket in the linked PSA with the suspect message attached, header details in the body of the ticket and the contact set as the reporting user.