Halo Service Desk Guides
Documentation to assist with the setup and configuration of the Halo Service Desk platform
N-Able Passportal Integration
N-Able Passportal Configuration
This integration requires some configuration within your Passportal instance before the integration configuration can be completed in the Halo Application.
Application URL, API Access Key and API Secret Key
To communicate with Passportal via its API, an API Key and Secret must be generated in Passportal. This can be done by following these steps:
Please ensure you copy the secret access key as you will need this in the next step.
The first section to complete is the Passportal details. Using the API Access Key ID and Secret Key generated in the previous step, you can fill out the fields here. For the application URL, you set the URL you use to access your Portal.
Once all three fields are complete, you can test your credentials using the "Test Credentials Button"
Before using any imports, please ensure every field on the Passportal configuration page marked with a red * is filled out.
Client/Location Import Configuration
You can import your Passportal Clients and their Locations into Halo.
If the clients you are importing already exist in Halo, please using the mapping table to link the existing Halo customer to the Passportal Client. This will ensure you do not create duplicate clients.
If you import a client which is not mapped, a mapping link will be created for future use.
Once any mappings are completed, you can use the Import Clients & location button to import your Passportal Clients/Locations.
You can import Contacts from Passportal as Users in Halo.
The only configuration option here allows you to map a default Client/Site to the imported Contact if they do not match a Client/Location that you would have imported in the previous step.
You can import Assets from Passportal into Halo.
The first option allows you to set a default Client/Site for the Asset if it does not match any imported Client/Location from Passportal.
Next, you can set the Asset group for Assets imported from Passportal.
If Assets you are importing already exist in Halo, you can use the Asset matching field to match a Passportal field to a Halo field and therefore match the Asset, to ensure no duplication.
The Asset Field mappings table allows you to map Passportal Asset fields to Asset Fields in Halo. On each import, these Asset Fields will be set/updated if they are mapped. You can also set the Passportal field to generate a new Asset Field in Halo when importing, if there is no existing Asset Field in Halo.
All three imports can be run on a schedule using the Halo Integrator. Please ensure you have updated the Halo Integrator otherwise it may not be compatible with this Integration.
To use this integration with the Halo Integrator, you must tick the "Enable the Halo Integrator for the N-Able Passportal integration" setting.
You can then choose which imports you would like to run on each Halo Integrator sync.
Finally in the miscellaneous settings, you can allow Assets in Halo to be made inactive if they are deleted from Passportal. Please note this will only have an effect if the import is through the Halo Integrator.
- Asset Import - CSV/XLS/Spreadsheet Method
- Call Management in Halo
- Creating a New Application for API Connections
- Creating Agents and Editing Agent Details
- Departments, Teams and Roles
- Halo Integrator
- Importing Data
- Multiple New Portals with different branding for one customer [Hosted]
- Organisation Basics
- Organising Teams of Agents
- Step-by-Step Configuration Walk Through
- Syncing Exchange Calendars