Host isolation for organization level admin/security engineer | Voters

Host isolation for organization level admin/security engineer

Hunter Mays

Admins and Security Engineers at the organization level should be able to isolate and de-isolate hosts.

It would be even better if we could have granular control over user roles. For example if we could create our own roles and select which individual permissions they should have.

July 24, 2025

Josh Ross

I would love to see this as well. Specifically, I would like this to be part of those granular controls "Admins: can view all escalations but can only respond to Unwanted Access (Country & VPN) escalations." I have to click the Remove button for certain escalations that the client has remediated but are unable to update in Huntress.

Autopilot

Merged in a post:

Custom User Roles

Andrew Stevenson

I was looking to see if there were was a way to make a custom role or adjust any of the permissions in the current roles this morning. I noticed a lot of posts related to request specific additions to Roles. It would be extremely helpful to have more granular, customizable role permissions and would help us all maintain our organization's and client's least privilege. 
For example, allowing a role to isolate an endpoint but not remove it from isolation without approval, or allowing visibility into ITDR escalations without the ability to close them.
Because each organization defines least privilege differently, this flexibility would be highly beneficial and would improve both security and operational efficiency.
Thank you for considering this request!

January 3, 2026

Patrick Burke

Excellent requests and we would welcome progress on both especially in relation to escalations.

Shawn Weisz

This seems to be a no brainer to me. We provide tools like RMM and Huntress where the customer has an internal IT team. They should surely be able to do this.