Generating the Client ID and Client Secret in Halo

1. Log into your HaloPSA account with an admin users permissions.
2. Select Configurations.
3. Scroll down and select Integrations.
4. Select HaloPSA API.
5. Next, click on the View Application button.
    
6. The Applications listing page will load.
7. Here, click on the New button in the upper right-hand corner.
8. In the Application Name field, enter .
9. In the Authentication Method, select Client ID and Secret (Services).
10. On the Permissions tab, check the All option.
11. Click Save.
12. Once saved, the Client ID and Client Secret will be created.
13. Save the Client ID and Client Secret.

Connecting the Halo Client ID and Client Secret into 1stream

1. Log into the 1stream Admin Portal.
2. Go to the Administration > Manage Organization menu in the top right. 
   
3. Scroll down to the Connected Account and CRM Settings section. 
4. Click on the green circled + to open the configuration pop-up.
5. Select HaloPSA in the CRM Platform drop-down.
   
6. Click the Save button. The pop-up will refresh with the connection configuration settings.
   
7. In the CRM Company field, enter your HaloPSA Company ID.
8. In the API Key field, enter the Client ID generated in Halo.
9. In the API Private Key field, enter the Client Secret generated in Halo.
10. In the Endpoint field, enter your Halo URL with api/ at the end of it. 
    • URL should look like https://xxxxxxx.halopsa.com/api/
11. In the CRM Details link, enter your Halo URL. 
    • URL should look like https://xxxxxxx.halopsa.com/ 
12. Click Save.
13. Scroll Up to the 1stream Administration section.
14. Click on the Systems Check link.
     

There will be a pop-up that appears and confirms if the connection was successful or if there was an issue that needed to be corrected. This will also pull in the user data from your Halo connection that will be reflected when users are added in the next section.
 
 

Mapping CRM Users

Once the CRM Connection to Halo has been completed, the users in 1stream can be now mapped to their corresponding Halo user.

For instructions on how this can be done, please see our Mapping CRM Users article.