Account, Org, and User Management

We have clients with employees who may go to a country, return, then go back again. Currently, we can't create a second rule for the same location while the initial rule is in place. This is inefficient for our clients who have employees who travel often as we have to then remember/create reminders to add the second rule once the first rule has expired.

I would like the ability to set Incident Notification Contacts at the organization level instead of the account level. This feature would be beneficial for IT Directors who need to receive phone or text notifications for critical incidents across the entire organization.

As an MSP we have some accounts that we co-manage with IT at their organization. We resell Huntress as a service. It would be great to be able to set admins at an account level to be able to manually isolate and deisolate hosts. This can be current admin or something like adding a checkbox that adds the permissions or a separate "super" admin that has the permissions. There are users that we trust to remediate issues at their organization. With remediation, the ability to remove isolation should be an immediate option at their discretion.

I would like to have the ability to create location-based rules using IP addresses. This feature would help in managing access and permissions based on the geographical location of users, enhancing security and compliance.

Partner would like for organizational Security Engineers/Admins to access the Escalations tab. Currently the link at the account level and Organizational level are inaccessible for Security Engineers/Admins at the Org level to resolve/look into. If they can customize the permissions that would also work. Currently it looks like any organizational role is not able to access the link to investigate and resolve the issue.

We need the ability to assign phone and SMS contacts per organization so that internal IT staff or designated responders for a specific client only receive alerts for their own environment. Example: in a co-managed setup, the client’s IT manager should receive Huntress alerts only for their organization, not for all others under our account. This feature would improve flexibility and reduce noise for MSPs while keeping the right people informed during critical incidents.

We would like to give certain customer user accounts the ability to respond to incidents and escalations at a sub-account or organization level. Currently, admins can only view but cannot respond. This feature would be beneficial for our customers who have their own internal IT teams capable of handling incident responses.

Depends on: https://feedback.huntress.com/feature-requests/p/unique-keys-per-organization We have yet to deploy Huntress outside of labs because our client sites require the ability to add devices themselves (co-managed). We explored creating custom tooling for this, but we haven't had the time to do so. We would like the ability for organization level Admins to download the installer and use their own unique organization key to register the device (ideally, up to a set maximum per org). This would also be the dividing line between organization level security engineers and administrators (as one doesn't currently exist, as the existence of the role is being reevaluated).

I would like to have the ability to tag specific accounts, such as Break Glass Emergency Access Accounts, for login alerts. This feature would enhance security by notifying me whenever these critical accounts are accessed, allowing for immediate response if necessary.

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