Account Level Admin Permissions to Manually Isolate/Deisolate Host
J
Jordon'la Heathcote'la
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.
J
Jeff Custer
We are also an MSP providing Huntress as a part of our services to our clients. We have many larger clients who have internal IT personnel who SHOULD have admin permissions over their tenant but don't because of the restrictions on org-level accounts. I just had a tense conversation yesterday with the internal IT manager at one of our larger clients about how his account is an "admin" but he "...can't even set travel exceptions or download an agent to install on a machine or basically any other admin-like thing" for their organization. He also was incensed by the fact he can't get any notifications other than ticket notification create by the integration between Huntress and our PSA. There are already two levels of permissions for org-level users--why not give the Admin-level actual administrator permissions?
A
Attila Puskas
We are joining the queue on this request. We also would like this feature to be available as an extra option that can be enabled for selected organizations/admin users.
R
Ralf Schwerdt
Definitly would be a big win.
So not only Account (reseller) Admin can isolate, but also Org. Admin / Org. Security Engineer.
Edit: Perfect for onboarding new customers, so they could also test how it would behave.
K
Karthik Devarajan
We absolutely need this!