Integrations, Webhooks, APIs

Syncro and RepairShopr are the same when it comes to API integration. It would be nice if there was the option to put in company.repairshopr.com instead of company.syncro.com

Hello Huntress Team, I’d like to request an enhancement for the CW Automate deployment method. Currently, the Huntress script uses the ClientName from Automate to create or map organizations. If a client name is changed, Huntress creates a duplicate org/site, causing devices to check in under multiple locations. Please consider allowing the use of unique ClientID/LocationID values (or a custom EDF) instead of ClientName. These IDs never change in CW Automate and would prevent duplicate org creation, simplify onboarding/offboarding, and keep policies/exclusions consistent. This improvement would make deployments more stable and reduce manual cleanup. Thank you,

Currently there is no way to enforce Duo out the gate for new users. You must login, setup Google Auth, enable Duo on your profile, delete Google Auth, and then you can use Duo.

Partner feedback on detections for endpoints potentially missing the Huntress agent via Defender for Endpoint integration: 'What [you] could do on your end is to request a new Health Status in the list when devices are 'Missing Agent' flagged. Maybe something like 'Active but not found in Defender portal' instead of just 'Active'' Context: endpoint in 'potentially missing agent' list was found to already have Huntress installed but Defender for Endpoint had incorrect details for system configuration on endpoint (i.e. Defender was picking up previous image of Windows 10 but device had recently been reimaged for Windows 11)

Having SAML SSO set up is great, including the ability to enforce it, thanks! As documented and in practice, when using iDP-initiated sign-in, it just redirects to the SSO login page and users must retype their password. SAML is much more powerful than this, and it would be great if iDP-initiated sign-in were as seamless as it is most places. Thanks!

We intergrated every enterprise company for financial benchmarking and collaboration.

If you accidentally delete an agent, there is no way to restore

As of the last time I looked the SAML 2.0 integration you guys have explicitly states that Passly SSO is not supported.