User and Organization/Account Management

Org level admin - respond to escalations - my client knows best where their users should be or shouldn't be - I would like them to be able to respond to the escalations - and select the Unauthroised / authorised

We would like to see the addition of FIDO security key support as a multi-factor authentication (MFA) option for logging into the Huntress tenant. As organizations increasingly adopt phishing-resistant authentication methods, FIDO2/WebAuthn has become a critical standard for securing access to sensitive systems. Why this feature matters: FIDO keys provide strong, hardware-based authentication, reducing the risk of credential phishing and account compromise. Many compliance frameworks (e.g., NIST 800-63, CISA Zero Trust guidance) recommend or require phishing-resistant MFA. Offering FIDO key support would align Huntress with modern security best practices and customer expectations. Benefits for Huntress and its customers: Enhanced security posture for administrators and partners. Improved compliance with industry regulations. Seamless integration for organizations already using FIDO keys across their environments. We believe this feature would significantly strengthen the security and usability of the Huntress platform.

It would be great if each organizations Command Center showed all of the Huntress Products (EDR, ITDR, SAT, SIEM) and a quick [active / inactive] indicator. I have Security Engineers that currently do not have a way to tell if an organization has ITDR. The Command Center is the perfect place for this high level overview, and is ALMOST already set up that way.

I would like the ability for organization-level users to receive their own alert emails for self-management. Currently, adding an email to the alert list means they receive alerts for every account, which is not ideal. It would be beneficial to have a feature that allows specific users within an organization to manage their own alerts independently.

Admins and Security Engineers at the organization level should be able to isolate and de-isolate hosts. It would be even better if we could have granular control over user roles. For example if we could create our own roles and select which individual permissions they should have.

Adding the ability to purchase SAT, SIEM and ITDR directly from the Huntress portal

Looking to have the ability to change the point of contact listed on the message users receive when an endpoint is isolated at the org level.

We have a client who manages his own clients, and likes the branding to be his. However, the name of our main account shows up at the bottom of the "Isolation messages" which are displayed for his clients. I see that the report are banded. Can the isolation messages, (and any other branding visible to the end user), be branded for our client?

I need my engineers to have full control over our customer organizations without having access to our own Huntress environment. Currently, Organization-Level Security Engineers have similar permissions to Organization-Level Admins, which doesn't allow for this separation. It would be beneficial to have a role that allows engineers to manage customer organizations while restricting access to our own instance.

I would like to have the ability to mark multiple countries as Unauthorized in one go, except for the US and UK. Currently, I have to mark each country individually, which is time-consuming and inefficient. It would be beneficial to have a feature that allows me to select multiple countries at once to streamline this process.