HowTo: Integrate CyberHoot with HaloPSA (Autopilot Platform)

This guide walks you through setting up and managing the CyberHoot–HaloPSA integration using the CyberHoot Autopilot Platform. Once connected, the users of the HaloPSA clients you map to CyberHoot tenants are automatically enrolled in CyberHoot cybersecurity training and kept in sync every night.

What the integration does:

• Clients: HaloPSA clients that you map to CyberHoot tenants have their users synchronized into CyberHoot.
• Users: every active user of a mapped client who has an email address is added to CyberHoot for cybersecurity training. Users marked inactive in HaloPSA are skipped, and archived in CyberHoot if they were previously synced.
• Schedule: synchronization runs automatically once a day, around 12:30am in your deployment’s time zone. You can also run it on demand with Sync Now.
• Read-only: CyberHoot only reads clients in your HaloPSA instance and users of those clients. It never writes to your HaloPSA instance, and it only uses this information for cybersecurity training.

1. Create API credentials in HaloPSA:

CyberHoot needs API credentials to talk to your HaloPSA account. Create them in HaloPSA first, then bring them to CyberHoot.

1. In HaloPSA, go to Configuration > Integrations > HaloPSA API.
2. Under Applications, click New and name the application CyberHoot.
3. Set the Authentication Method to Client ID and Secret (Services) and choose the agent the application should act as.
4. On the Permissions tab, grant read-only access to customers (clients) and their users. CyberHoot never writes to HaloPSA, so no edit or delete permissions are needed.
5. Save the application, then copy the Client ID and Client Secret. The secret is only shown once, so store it somewhere safe.

You will need the following values in the next step:

• HaloPSA Instance URL – your HaloPSA web address, for example https://yourcompany.halopsa.com.
• Client ID – the Client ID of the API application you created in HaloPSA.
• Client Secret – the Client Secret generated for that application.

2. Connect to CyberHoot on Autopilot:

• On the CyberHoot Autopilot platform, navigate to Partner Dashboard > Integrations.
• Select HaloPSA and click “Get Started”.
• Enter the values you collected in step 1: HaloPSA Instance URL, Client ID, Client Secret.
• Click “Connect to HaloPSA”. CyberHoot validates the credentials against HaloPSA before saving them.

Note: If the connection fails, double-check the HaloPSA Instance URL and make sure the credentials were copied without leading or trailing spaces.

3. Map Clients and Sync:

• On the same page, click “Map Clients”. CyberHoot lists every client in your HaloPSA account on the left with a drop-down of your CyberHoot tenants on the right.
• For each HaloPSA client you want to train, pick the matching CyberHoot tenant from the drop-down. You can also choose Create as a new Automatic tenant (training starts the next day) or Create as a new Power tenant to have CyberHoot create the tenant for you.
• Click “Map Clients” at the bottom of the window to save the mappings.
• Click “Sync Now” to perform the first synchronization. The Sync Log shows how many customers were updated and how many users were added, updated or skipped.

Note: When looking at the users within a mapped CyberHoot tenant, the user “Type” will show as “HaloPSA”.

4. Ongoing Management:

• New users added to a mapped client in HaloPSA are picked up automatically at the next nightly sync (or immediately with Sync Now).
• To stop training a user, mark them inactive (or remove their email address) in HaloPSA. They are archived in CyberHoot at the next sync.
• To start training a new customer, map their HaloPSA client to a CyberHoot tenant using “Map Clients”.
• The Last Sync Time and Sync Log on the integration page show what happened during the most recent run.

5. Removing a Client:

• On the CyberHoot Autopilot platform, navigate to Partner Dashboard > Integrations.
• Select HaloPSA and click “Map Clients”.
• Click the red “X” next to the client you want to remove, then click “Map Clients” to save.
• Click “Sync Now” to complete the removal.

Note: Unmapping a client archives all synced users of that tenant in CyberHoot. You can easily add them back by mapping the client up again and running a sync.

6. Disconnecting Integration (If needed):

• On the CyberHoot Autopilot platform, navigate to Partner Dashboard > Integrations.
• Select HaloPSA and click “Disconnect”.

Note: Choose the option below carefully.

If you want to continue using CyberHoot without the integration with HaloPSA, choose “Disconnect & Set Local”. This will set all synced users to be locally managed within CyberHoot.

If you plan on archiving all synced users within CyberHoot after disconnecting, select “Disconnect & Archive”.

Disconnecting removes the integration settings and client mappings from CyberHoot. CyberHoot never changes anything in your HaloPSA instance.

Other CyberHoot integrations:

• SyncroMSP
• Gradient MSP
• ConnectWise PSA
• Autotask PSA
• IT Glue
• Hudu
• CloudRadial