HaloCRM Guides

Jamf Integration

The Jamf integration is able to import Mobile Devices and Computers over from Jamf into Halo, it also has the ability to integrate with multiple Jamf instances. For each tenant created, you'll first need to input your Jamf Url, followed by a jamf account username and password alongside setting asset types to import and default asset types for each asset type being imported:

The default site will get all of the assets that were not matched on to sites or users. The site matching type selected below will give the site mappings precedence over the site of the user that is matched. The account will need at minimum read permissions for mobile devices and computers endpoints. The other options for type are using the matched user's site only or using site mappings to determine the site from the Jamf device's building only. The other is fail safe, using the site mappings and falling back to the user's site if a mapping for the Jamf device's building is not present.

Asset Field Mappings Table.

When adding fields to the asset mapping, you will be shown the following fields:

If the field type chosen is "Custom Field" you can choose a field in Jamf to match a custom field to in Halo (Entity must be "Asset" check out the custom fields guide in the HaloPSA Academy for more info: Guide). Extension Attributes can be mapped to Custom Fields or Asset Fields.

Advanced settings are for syncing assets/ asset types or not. The Jamf integration does not include a multi select option for choosing the entities to sync, as their is only the option of assets. Instead it has an option to not update asset types ("Do not update Asset Types"). You can also set it to not create new assets in Halo, this again refers to when the integrator runs and syncs assets, you can choose to not let new assets be created in Halo when the sync runs.