Before you start
An active ConnectWise Manage integration in Huntress that is already opening tickets. See ConnectWise Manage PSA - Incident Report Integrations.
ConnectWise security access to edit setup tables. If Manage Hosted API isn't listed, grant it under System > Table Setup > Customize > General / Manage Hosted API.
A Huntress login for each technician. Actions are recorded against the user who takes them, so shared logins aren't supported.
Replace yourcompany below with your Huntress address, for example https://yourcompany.huntress.io.
1. Add the pod
Go to System > Setup Tables > General > Manage Hosted API. Search for
Manage, since the search matches from the start of the name.Click + (New). The row under the column headings is a search filter, not the new entry.
Fill in the fields and save.
Field |
Value |
|---|---|
Description |
Huntress |
Screen |
Service Ticket |
Origin |
|
URL |
|
Tab / Pod |
Pod |
Pod Height |
660 |
Location Restrictions |
Leave Enable unchecked |
Tab / Pod defaults to Tab, so change it. Origin is scheme and host only, with no path or trailing slash.
2. Show the pod on the ticket screen
Open any service ticket, click the gear icon at the top left, choose Pod Configuration, move the Huntress pod to Displayed, and save.
3. Sign in
Open a ticket Huntress opened and click Load from Huntress.
Web client: sign in through the pop-up. SSO and MFA work as usual. Approve access the first time; after that the pop-up opens and closes on its own. Allow pop-ups for your Huntress address.
Desktop client: the pod shows a code and opens a Huntress page in your default browser. Sign in, enter the code, and approve within 5 minutes. You stay signed in for up to 8 hours or until you close the client. Only enter a code shown in your own pod.
What you can do
Escalations:
Resolve. For Unwanted Country Access and Unwanted VPN Access, choose Expected or Unauthorized, then a scope: These identities only, Everyone in this organization, or Everyone in this account. Expected decisions can have an expiration date.
Revoke access and disable identities is recommended. If you clear it, current sessions are left alone, but future sign-ins are still treated as unauthorized.
Dismiss closes the escalation without a rule. It reopens if the activity happens again.
A resolution applies to every identity on the escalation, even if the ticket names only one.
Incident reports:
Approve the remediation plan. This approves all pending remediations. You can mark any you'll do yourself instead of Huntress.
Reject the plan with a reason. It goes back to the Huntress SOC to revise and re-issue.
Mark manual remediations done.
Comment, up to 2,048 characters.
Resolve, or Resolve and Release Containment if the report includes containment.
You only see the records and actions your Huntress role allows. Read-only users can view but not act.
After any action, reload the ticket to see its status update.
Troubleshooting
Message |
Fix |
|---|---|
This Huntress pod isn't available |
Check that the URL uses your Huntress address and your ConnectWise integration in Huntress is active. If both are correct, contact Support. |
Refused to connect |
The address you open ConnectWise on must match the ConnectWise server in your Huntress integration. For cloud, |
No pod on the ticket |
Repeat step 2 on the Service Ticket screen. |
No Huntress escalation or incident report |
Normal for tickets Huntress didn't open. |
More than one Huntress record |
Contact Support with the ticket number. |
Sign-in did not complete |
The code wasn't approved within 5 minutes. Click Load from Huntress again. |
The user code is invalid |
Re-enter the code exactly as shown, signed in to the same Huntress account. |
Could not save that change |
Try again, or take the action in the Huntress portal. |
For anything else, contact Huntress Support with the ticket number, whether you use the web or desktop client, and a screenshot of the pod.