Summary and recommendation
Huntress user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Huntress user management lives entirely inside the Partner Portal at https://partners.huntress.io under Settings > Users.
The permission model is role-based with exactly two fixed roles - Account Admin and Standard User - and no granular permission toggles or custom roles are documented.
Role assignment happens at invite time and can only be changed by an existing Account Admin.
Quick facts
| Admin console path | Settings > Users (within the Huntress Partner Portal) |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Account Admin | Full access to all portal features: manage users, billing, organizations, agents, reports, and respond to incidents. Can invite and remove other users. | Only Account Admins can manage other users and adjust account-level settings. | |||
| Standard User | Can view detections, reports, and managed organizations assigned to them. Can interact with incidents but cannot manage users or billing. | Cannot invite or remove users, cannot access billing settings, cannot modify account-level configuration. |
Permission model
- Model type: role-based
- Description: Huntress uses a fixed role-based model with two primary roles: Account Admin and Standard User. Roles are assigned at invite time and can be changed by an Account Admin. No custom roles or granular permission sets are documented.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse - two fixed roles with no documented per-feature permission toggles.
How to add users
- Log in to the Huntress Partner Portal at https://partners.huntress.io.
- Navigate to Settings > Users.
- Click 'Invite User'.
- Enter the invitee's email address.
- Select the desired role (Account Admin or Standard User).
- Click 'Send Invite'. The invitee receives an email to set up their account.
Required fields: Email address, Role selection
Watch out for:
- Invitations are sent via email; the invitee must accept before the account is active.
- Only Account Admins can send invitations.
- No documented bulk CSV import for users.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Huntress official documentation describes removing users from the portal. Account Admins can remove a user, which revokes their portal access. The official help article uses 'remove' terminology; whether this is a hard delete or a deactivation/soft-delete is not explicitly distinguished in available documentation.
- Log in to the Huntress Partner Portal at https://partners.huntress.io.
- Navigate to Settings > Users.
- Locate the user to be removed.
- Select the option to remove the user.
- Confirm the removal.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- Only Account Admins can remove users.
- The official documentation does not explicitly describe what happens to data or records associated with a removed user.
- Ensure at least one Account Admin remains on the account before removing an admin user.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Endpoint Agent | Per-endpoint billing for managed detection and response coverage on a device. | Custom pricing; contact Huntress sales or refer to partner agreement. |
- Where to check usage: Huntress Partner Portal > Reports or Billing section for endpoint/agent counts.
- How to identify unused seats: Not documented
- Billing notes: Huntress pricing is endpoint-based (per agent), not per portal user seat. Adding or removing portal users does not directly affect billing. Pricing is custom and negotiated through the partner program.
The cost of manual management
Huntress billing is endpoint-based (per agent), not per portal user seat, so adding or removing portal users has no direct effect on your invoice. Pricing is custom and negotiated through the partner program; no public per-seat figures are available.
License utilization is tracked through the Reports or Billing section of the Partner Portal, where endpoint and agent counts are visible.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
If your team is small and role granularity is not a requirement, the two-role model is straightforward to operate. For MSPs managing frequent staff turnover or needing scoped access per technician, the coarse permission model and fully manual provisioning workflow create meaningful ongoing overhead.
There is no native path to automate user lifecycle from an IdP, so every app onboarding or offboarding event requires a manual portal action.
Bottom line
Huntress portal user management is functional but deliberately minimal: two fixed roles, invite-only provisioning, and no bulk import or IdP integration. For small, stable teams this is workable.
For MSPs with high technician turnover or compliance requirements around access scoping, the manual overhead and coarse role model are real operational constraints worth factoring into your tooling decisions.
Automate Huntress workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
