Account/Organization/User Management

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

Enable Point of Contact in Huntress portal to be a non-admin user. Currently the Point of Contact must be a Huntress Admin, which means that we need to allocate Huntress Admin access to a user's standard email address, as that address is the best contact for Huntress to reach out to during an incident. We want to give Security Engineer access to our engineers' standard accounts and only provide Huntress Admin access to separate/dedicated privileged accounts. However, this change would necessitate making a privileged account the Point of Contact, and those mailboxes are not well monitored by the engineers (if they even have a mailbox!), so contact from Huntress may be missed during an incident.

Please give us some Phishing resistant login functionality for the Portal, OTP is not enough especially for a security platform

I changed my email address, didn't get the confirmation email. Now the field just displays the email address with the banner: "E-Mail Address (unconfirmed)", and there is no way to change it to a different one. Either give the option to resend the confirmation email or allow to change the email address.

Currently they can see escalations but cannot take action. This makes things difficult for our clients that have their own IT staff and want to manage this themselves.

For the MSP model we think that allowing for direct chat interactions between the client and Huntress would really bring out the value of Huntress. Key benefits that I can think of: -Even small businesses with under 50 licenses would be able to use the Chat feature. -Clients looking for 24/7 coverage where the MSP might not would not be hindered.

Examples of different roles that would aid in "least privileges" to comply with audits: Sales & Billing roles, master Account Admin, tech admins that can work on client administration, etc.

On our other platforms we have SSO enabled and enforced, but we have a role we can give to certain users that are outside our organization, like one of our clients we manage has an on-site IT person we work with whose email does not match our domain. With this role he can log in direct with password. Others in the our organization who can log in through SSO also have this role and it allows them to log in direct if they choose which is helpful when there is an issue with SSO or the Identity Provider, we are not locked out of our system. That is not the case here yet. We would have to enforce SSO and not allow Anthony or other outside colleagues to view their companies' machines. This creates a potential lock-out if there is an SSO issue or Identity Provider issue. The other option is not an option, not enforcing SSO, because Huntress still requires MFA. This makes SSO pointless since we still need to pull out our phones for an MFA code, so that's a non-starter. Please add a role or account exemption that organizations can add to Huntress user accounts that will make SSO optional for them, they can use SSO (with the MFA required by our identity provider without additional huntress MFA) or they can log in direct, with user+pass+Huntress MFA.

When adding new admins in the Huntress Portal, we would like the ability for existing administrators to copy the 'invite email' or 'invite link' for the new user directly from the Admin console instead of users actually having to actually receive the invite emails directly. Many of our admin/email accounts for access to Huntress are not accounts that have mailboxes. For example, my day to day account might be first.last@mycompany.com and my Admin account for signing into Huntress and other tools is SU-first.last@superuser-mycompany.com . We do enforce SAML SSO in Huntress and have special Conditional Access policies in M365 for the SU accounts to protect them. I invite a colleague, ' su-colleaguefirst.last@superuser-mycompany.com '. That mailbox doesn't exist, but it is a valid Entra account with the ability to do SAML SSO. I'd like to be able to copy the invite link myself after adding the user, and send the invite to the user themselves, instead of relying on an email to be delivered to a mailbox. Primarily, this is because it's best practice for the usernames/email addresses we use to sign into privileged platforms like Huntress and to manage our other MSP client accounts are different than our day-to-day working accounts.

We have to have our Huntress account, and since your Zendesk is not integrated, we also have to have a Zendesk account, and now when support sends us to this feedback board, to 'hope and wish' something gets fixed, we have to create a third account for here. Besides being disorganized and looking like a disjointed system, it's not convenient or appreciated.