HaloPSA / HaloITSM
Works with: Halo Cloud and on-premise. What SafeHanded does in Halo: private notes on every step · a customer-visible reply for link delivery · close-to-purge · request from a ticket · optional chain-of-custody certificate attachment.
Before you start
Section titled “Before you start”- A Halo administrator, and a SafeHanded Owner/Admin on the Team plan or above.
- About ten minutes.
1. Connect
Section titled “1. Connect”- In Halo, create a client-credentials application under Configuration → Integrations → HaloPSA API with the agent scope, and note its Client ID and secret. (Halo API authentication)
- In SafeHanded: Settings → Integrations, choose Connect and pick HaloPSA / HaloITSM. Give the connection a name, enter the Halo URL, Client ID and Client secret (and, under Advanced & optional settings, the Tenant for hosted instances), then click Connect and test.
2. Close detection
Section titled “2. Close detection”Nothing to set up. SafeHanded polls Halo for status changes, so resolving or closing a ticket purges its credential on the next poll. SafeHanded re-reads the ticket via the API before anything is purged — see how ticketing works.
3. Request from a ticket (deep link)
Section titled “3. Request from a ticket (deep link)”Halo can add a custom button to the ticket screen.
- In Halo, add a custom button for tickets, labelled Create SafeHanded request, that opens a web address.
- Paste the link below as its address. Then replace
TICKET_IDat the end with Halo’s variable for the ticket ID. - Save. Technicians click the button on a ticket to open a new SafeHanded request linked to it.
https://safehanded.com/app/requests/new?ticket=TICKET_IDTo copy this link, open Settings → Integrations, select your Halo integration and go to its Activity tab.
Choosing a preset (optional). A preset is a saved request — the reason, how long the credential is kept, who receives it and how the link is sent. To start from one, add &preset= and the preset’s slug to the end of the link, for example &preset=password-reset. Each preset’s slug is shown, with a copy button, under Settings → Request presets. With no preset in the link, SafeHanded uses the client’s default preset, then the organisation default (Settings → Policy → Default preset for new requests), and otherwise the policy defaults.
4. Status mapping
Section titled “4. Status mapping”Halo status names map to open / pending / resolved / closed out of the box; override anything custom
under Status mapping on the integration’s Configuration tab. Only a status that maps to your purge trigger
destroys a credential.
What technicians see
Section titled “What technicians see”Private notes when the request is created, submitted, revealed (if enabled) and destroyed — the final note names when and who closed the ticket, where Halo reports them. With Attach the chain-of-custody certificate to the ticket turned on in your policy, the signed custody certificate PDF is attached on purge.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause / fix |
|---|---|
| Test connection failed | Check the application scope is agent and the secret is current. |