Managed EDR

The partner is using tags as locations / sites to separate their customers. These do not carry over to the Billing section which would be helpful to break down the billing per location / site. Currently, the only work around is to create multiple organizations to achieve this.

Submitting this on behalf of a partner that relies on ConnectWise as their source of truth and feels our CW integration is incomplete because it (1) doesn’t create Huntress orgs from CW companies or surface unmapped CW companies for create+map in one flow, and (2) doesn’t let them control how Huntress severities map into their own ticket priorities. For macOS/MDM, they see the current org-key model as forcing them to “recreate every company” in Huntress and introducing human error, instead of simply selecting unmapped CW companies and having Huntress create/link orgs automatically. On the alerting side, they’re frustrated that Unwanted Access rules plus Huntress’ severity model result in Critical incidents they didn’t choose, and they have to build compensating logic in CW to restore their own impact/urgency-based prioritization. Their request is: add a proper CW-driven org auto-creation/mapping experience, and give partners more control over how Huntress severities translate into PSA ticket priority.

It could be very clear on the first page of Assignment creation which account this Assignment will be applied to. It is currently possible to navigate back in the browser in between creating assignments and accidentally change the Account, which is barely noticable during the creation of the assignment.

Enable the control of Bitlocker from the huntress portal. Also Bitlocker Key storage.

We have customers who are non-profit or education and generally have high security requirements with low budget. If we could offer discounts for charitable or edu orgs we could push alot more, especially MDR.

Currently all notices such as [Huntress] Unresponsive Agents Uninstalled appear to send to the billing contact or myself as the admin however they should be sent to my team to verify and action. Please make that a configurable item so I can direct it to my alerts team.

Please provide the Escalation "Login without Entra Usage Location" as a per-identity basis escalation. We then can get a per-identity notification for every new escalation. At this point we do not get any email notification for a new escalation if there already was a escalation for a different user in the past.

Add a way to specifically toggle the Escalation has been resolved Notification to off or be able to route these to a specific email.

There are scenarios where an agent may be accidentally installed on a duplicate organization. When you perform the agent move to correct the organization assignment for the agent the Incident Report does not also move over. It would be nice to have the incident report automatically move over to keep the information for historical purposes. Or an ability to manually move them is an option too.

Most alerts have the respective customername in the title, only escalation is overdue has no trace of which customer it is. Would be nice to have it present in the subject. See attachment for reference.