Integrations

Ability to create email integrations at the organization level so incident reports for certain organizations will be sent to them and not the account level emails.

We would like to receive only incident tickets via the Autotask PSA integration, not escalations. We do not see an option to disable escalation tickets and lack the capacity to investigate them individually. Ideally, we would like to dismiss them and review escalations in the portal when needed.

I don't have any clients who use Windows Defender. It would be great if in the future there was a Sentinel One integration to pull logs from and review detentions to confirm that Sentinel One completely removed the threat.

Let's say I received an escalation with the subject "Unexpected Country - United Kingdom." The escalation involved one identity and it created an Autotask ticket. After responding to and resolving the escalation, I have closed the Autotask ticket. The next day, I received another escalation with the same subject, but a different user was added this time. This caused the escalation to be re-opened, although the Autotask ticket was not re-opened. Is it possible to create new tickets based on a user being added to the escalation, rather than creating tickets for the escalation itself?

We would like to know when we can use ticket types in HaloPSA that have mandatory fields, so this issue can be closed - https://support.huntress.io/hc/en-us/articles/22491122152723-Halo-PSA-Ticket-Integration Note: If you are using Mandatory ticket fields within HaloPSA outside of "Ticket Type," the Huntress integration will not be able to create tickets and will error. While we work on addressing this feature to allow for future use of other required fields, you may opt to remove the mandatory field option within HaloPSA or choose a different ticket type without mandatory fields to allow the integration to run correctly.

We would like the ability to decide the ticket type to be used on an escalation vs an incident. For example, we consider Huntress "Incidents" a critical priority and want this to create an "Incident" ticket in Halo, whereas we are happy with "Escalations" going to our alert ticket type.

The ability to pull data from Huntress to platforms used to track and consolidate GRC would be a wonderful tool for audits and tracking. We use Drata, but generally speaking, it would be nice to pipe the data in via API or integrations.

Addition of the following Ticket Mappings: Source: e.g. Phone, Monitoring Alert Issue Type e.g. RMM Alert Sub-Issue Type e.g. Huntress

The ability to export the ConnectWise Billing Sync Results to a CSV would be greatly appreciated by our finance team.

We enabled SSO with Microsoft Entra. It still requires us to manually create the user within Huntress before they can login. Many other applications that we integrated have an "auto provision" setting. When enabled this will automatically create the user in Huntress as long as they're part of security group on the Entra Enterprise Application. Some of the better ones even have mapping logic where you can map specific Entra Groups to specific permissions on the application (huntress) side.