Account/Organization/User Management

It would be great, to have the possibility to have a full Branding-Possibility as an MSSP. That means: Logo on Plattform Full Branded Reports Custom URL Name of Agent As an MSSP, this is important for as, as we want to push our own Brand. For Huntress this is not a disadvantage, as we could push our Services even more and have some advantages over competitors. It's not that great for us, to let our competitors see, with what for partners we build our services. We have already decided to not install Huntress on some special customers and using another SOC where we have this possibility, just because of this. In other cases we build a Webplattform-Overview, where we put all informations, which are important for an enduser, by API. So that the customer see whats going on, without having to know, that there is huntress in the background. But as we love Huntress, we really would love to have this possibility as a native option in huntress. By the way: even to have an agent on steroids would be great. If the agent (when rebranded) can be set viewable, so that the customer allways see it (as example in the tasklist) and has the possibility to send a message to us over it in case of a security question, would make the whole thing even more integrated. And for the customer: it doens't pay for something he just has to trust, that we're doing something for him, but he has the chance to involve himself with that, that would be a great option in my eyes... Just like you can do it with NinjaRMM, to make an example.

Examples of different roles that would aid in "least privileges" to comply with audits: Sales & Billing roles, master Account Admin, tech admins that can work on client administration, etc.

We would like to give certain customer user accounts the ability to respond to incidents and escalations at a sub-account or organization level. Currently, admins can only view but cannot respond. This feature would be beneficial for our customers who have their own internal IT teams capable of handling incident responses.

I manage multiple organizations and adding them one by one is time-consuming. It would be great to have a feature that allows me to bulk add organizations to streamline the process.

I need my engineers to have full control over our customer organizations without having access to our own Huntress environment. Currently, Organization-Level Security Engineers have similar permissions to Organization-Level Admins, which doesn't allow for this separation. It would be beneficial to have a role that allows engineers to manage customer organizations while restricting access to our own instance.

I would like the ability for organization-level users to receive their own alert emails for self-management. Currently, adding an email to the alert list means they receive alerts for every account, which is not ideal. It would be beneficial to have a feature that allows specific users within an organization to manage their own alerts independently.

I am interested in applying rules to the Huntress service account to restrict access only to Huntress datacenters or our technicians on our ZTNA. This would enhance security by ensuring that only authorized entities can access the service account.

It would be helpful to have roles auto-provisioned based on the enterprise app assignment. This feature would automate the role assignment process, reducing manual work and potential errors, and improving efficiency in managing user roles.

I need to create an organization user who can receive notifications for all investigations, incidents, and escalations, and view them in the console. However, this user should have read-only access to ensure they cannot make any changes.

Adding the ability to purchase SAT, SIEM and ITDR directly from the Huntress portal