Important Note: To automatically create assets in Incident IQ from Jamf, you must enable the create asset option and have location and models mapped in their respective tabs. Failure to do so can prevent some or all of your assets from importing/updating during scheduled syncs.
Accessing App Management
You can edit installation information using the management options.
Go to the Apps Management page by selecting Incident IQ Apps > Manage on the left navigation bar.
Locate your desired MDM application and select Manage to the right.
Overview Tab
Use this tab to review sync performance.
View Detailed Log: Opens the history of the last scheduled sync.
Start Full Sync: Manually trigger a new sync.
Re-Run Last Sync: Repeat the most recent sync process.
Push Data: Send data directly to the MDM integration
General Settings Tab
This tab controls automatic sync triggers, field mappings, and integration behaviors.
Authentication Section
View and manage authentication credentials:
Username
Password
Instance URL
Jamf Pro App Authentication
The account used to authenticate the Jamf Pro integration in iiQ must have specific permissions to enable this functionality. By default, most admin accounts have the necessary privileges to perform these actions.
Mapping Section
Create Asset: Automatically creates an iiQ asset for every new device discovered during a sync.
Update Asset: Automatically updates existing iiQ assets based on new data discovered during a sync.
Delete Asset: Automatically delete an iiQ asset during a sync if removed from the integration.
Import Options Section
Create Rooms Option: Automatically create rooms for assets found in the integration if they do not already exist in Incident IQ.
Update Asset Owner: Automatically update the owner in iiQ based on the primary user in the integration.
Unassign owner if primary user is blank: Automatically removes the owner in iiQ for assets that have an empty primary user in the integration.
Unassign owner if primary user can’t be matched: Automatically removes the owner in iiQ for assets where the primary user field can’t be matched to a valid user in iiQ
Matching Rules Section
This section controls how devices are matched. These rules are read-only for customers (editable by iiQ Admin Employees):
Use the serial number as the primary matching identifier.
Prefer the serial number over the asset tag.
Skip creation if the Google asset lacks a serial number.
Allow only one asset per serial number.
Restore deleted assets if a match is found.
Map Custom Values Section
Map additional values to default or custom fields in iiQ:
Click ‘Add’ located near the end of the section.
Please note that there may be pre-configured mappings that cannot be changed.
Select the custom value.
Set Map Direction:
MDM to Incident IQ
Incident IQ to MDM
Both directions (Data pushes from iiQ to the MDM first)
The following fields are supported to write back from iiQ to Jamf Pro.
Asset_tag
Location:email_address
location:realName
Location: username
Location: building
location: room number
Please note that the username field only accepts usernames for users already in Jamf.
When writing back to a location categorized as a building, ensure all your iiQ locations are configured as buildings in Jamf. If Incident IQ tries to write a value to a building field that is not present in Jamf, the update will not proceed, and no properties for that asset will be updated. As a result, the asset will be skipped.
Clearing the Owner Field: If an asset has a Username in Jamf, Incident IQ cannot clear other owner fields, such as the email address. While Jamf will accept the asset, it will leave the email address unchanged. To clear the owner information, the district has two options:
Set up a mapping that clears both the Username and email address. If the Username is cleared, the email address will be removed as well. The problem arises when attempting to clear the email address without first clearing the Username.
Ensure that assets do not have a Username assigned in Jamf. If no Username is set, there will be no issues clearing the email address.
Select iiQ Field: Map to a default or custom field. (Custom fields require a field name, type [text/number/date], and searchability settings).
The Jamf Pro account requires permissions to update computers, mobile devices, and users.
Perform Actions on Jamf-managed Devices Section
Manage whether authorized users can remotely manage devices in Jamf:
Enable remove device actions in Jamf: Allows remote device actions for users with permission to do so.
Location Mappings Tab
Manage how locations sync between Incident IQ and the Google Device App.
Location is required for an asset to be created in iiQ.
Default Mapping Section
Set or change the default location for assets with no specific location mapped.
Custom Mapping Options
Auto-Map Location Names: Automatically matches location names between the two systems.
Manual Selection: Manually search for and select specific location assignments if necessary.
Map by Owner’s Location: This feature automatically assigns an asset to its owner's location. This will only be available if one of the following Site Options is enabled:
When User is Assigned an Asset: Update Asset to Match Owner’s location
When User is Assigned an Asset: Update Asset to Match Owner’s room
When User’s Location Changes: Update Asset to Match Owner’s location
When User’s Room Assignment Changes: Update Asset to Match Owner’s room
Model Mappings Tab
Select or modify model mappings to ensure devices are correctly categorized in iiQ.
Unmapped models will not be imported into iiQ.
Auto-Map Models: Attempts to match device models from your list with existing models in iiQ.
Manual Mapping: Use the drop-down menus next to each device to select the correct model.
Create New Model: If a device does not auto-map and isn't in the drop-down list, click this button to automatically create and activate the model during the next data sync.
Sync History Tab
Provides a historical log of every synchronization attempt between iiQ and the integration.
Sync Details: Clicking any entry in the list displays a breakdown of the sync, including which devices were updated, created, deleted, or skipped.
Audit Filtering: Use the filter options at the top of the list to narrow your review by status or time.
Asset History Tab
Searchable database of basic device information found in the integration.
Search: Enter a valid serial number to retrieve specific device information.
Available Metadata:
External ID
Model
Owner Email
Organizational Unit
Serial Number
Location Name
Action Log: View a history of actions applied to the device during recent system syncs.
Remote Device Actions
Found within the General Settings tab at the bottom of the page, you can enable remote device management, allowing authorized administrators and agents with the correct permissions to interact with devices directly from the asset’s details page in Incident IQ.
Available Actions
Lock Device
Disable Lost Mode
Enable Lost Mode
Restart Device
Wipe Device
You can perform actions on the asset details page.
Configuration & Permissions Notes:
Default Access: Administrators are granted full access to all remote feature permissions by default.
Granular Control: Each remote feature listed above is controlled by an individual permission, allowing for customized access levels per agent.
Permission Management: Configure these settings under the App Specific section on the policies and individual user permissions pages.
Additional Steps for Enabling Lost Mode
Before initiating the "Enable Lost Mode" remote action, agents are required to provide at least one of the following:
Lost Mode Message
Lost Mode Phone Number
Optional Customization
Agents may also optionally add a footnote message that will display on the mobile device's Lock Screen once it has been placed in Lost Mode.
Developer Notes & Requirements
For additional technical notes on this functionality, including requirements for device compatibility with remote device actions, refer to the Jamf Pro API documentation.
