The Google Device App allows school districts to manage, create, and assign assets to students in Incident IQ (iiQ) using Google data. Integrating Chrome devices provides a single source of truth for asset metadata, including basic device information, OS/firmware versions, and Google identifiers.
Important Note: To automatically create assets in Incident IQ from the Chrome Console, you must enable the Create Asset option and ensure Location and Models are mapped in their respective tabs. Failure to map these may prevent assets from being imported or updated during scheduled syncs.
Google Admin Device Permissions
Adjust your Google device permissions based on your integration needs:
Read-only: To allow Google to read data and push it to iiQ, grant the scope: Manage Chrome OS Devices (read-only).
Read & Write: To allow Google to read data and write back data from iiQ, grant the scope: Manage Chrome OS Devices (ensure all permissions are checked, including Manage Chrome OS Device Settings).
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 manage authentication and review sync performance.
Status Section
Displays the validity of your current authentication token.
Use the Options button to re-authenticate or remove console access credentials.
Sync Section
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.
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.
Update Custom Fields: Updates only custom field data defined in the Map custom values from googleDeviceData section.
Enabling Create Asset or Update Asset will generate additional configuration options.
Choose the default iiQ status for devices active in Google.
Optional: Set status updates to occur only when a change is detected in Google.
Important Note: To successfully create assets from the Chrome Console, you must enable the "Create Asset" option and ensure both locations and models are mapped in their respective tabs. Failure to map these will prevent imports/updates.
You can set a device’s status in iiQ to disabled, deprovisioned, or deleted from Google.
Updates: You can update the status only during syncs when Google detects a status change.
Lifecycle Options: You can set whether these devices should be created in iiQ if they do not already exist, remain in iiQ, or be deleted from iiQ entirely.
When a sync runs, iiQ compares assets using their serial numbers or asset tags. If found, it associates the records and updates them.
Keep device in IIQ (but don't create a new one): Prevents the sync from deleting an asset if it is no longer found in the MDM.
Keep device in iiQ (and create it if it doesn't exist): Ensures the asset is created in iiQ if it is missing.
Use case: Districts that have disabled or deprovisioned devices in the MDM (no longer in use) but want to retain records in iiQ for storage or inventory management.
Import Options Section
Create Rooms Option: Enabling this will automatically create rooms for assets found in the integration if they do not already exist in Incident IQ.
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)
Note: The fields Annotated Location, Annotated User, Annotated Asset ID, and Notes are currently supported only for syncing from iiQ to Google.
Select iiQ Field: Map to a default or custom field. (Custom fields require a field name, type [text/number/date], and searchability settings).
Create a rule to automatically write back from iiQ to Google without waiting for the nightly sync:
Show Content
Show Content
Suppose you want the custom value to write back to Google when the change was made in iiQ. Instead of waiting for the nightly sync. You can create an asset rule.
This is only available if your district purchased iiQ Assets.
Navigate to the Rules Engine. When creating an asset rule, select the Action: Push asset changes to Google.
Review our help guide on Rules Engine with Assets.
MDM Options Section
Control how iiQ updates the owner field using the following drop-down options:
Don’t automatically update asset owner in iiQ: Disables owner field synchronization.
Automatically update owner in iiQ based on annotated user in Google: Uses the Google Console "Annotated User" field.
Automatically update owner in iiQ based on the last device user in Google: Uses the previous log-in user from the Google Console.
Additional Owner Options (if either automatic update is selected):
Remove existing owner in iiQ if the MDM field is empty.
Remove existing owner in iiQ if the MDM field cannot be matched to a valid user.
If the setting is "Don't automatically update asset owner in iiQ," the filter settings will not be displayed.
Additional Write Back Options Section
Manage how data is written back from Incident IQ:
Write device status to Google: Allows users to disable, re-enable, and deprovision devices from within the iiQ asset detail page.
Write orgUnitPath to Google: Updates the OrgUnit path in the Google Admin Console based on iiQ filtering (Role, Grade, Location, Model, etc.).
Note: Requires the OU to exist in Google and a pre-configured mapping in iiQ.
Important Note: It is highly recommended that you regularly back up your Chrome Cloud device data. Changes made by write-back options cannot be reverted through Incident IQ. If you have questions about these options, please consult with iiQ Customer Service before enabling them.
Batch Assign Users Tab
Use this tab to manually assign devices to users based on the device's "last user" data.
Update Suggestions: Click this button to pull the latest user login data report.
Filter: Add inclusion or exclusion filters to narrow the scope (e.g., exclude devices in the "/kiosk" Organizational Unit).
Generate Preview: Review the proposed assignments.
Assign: If the preview is correct, click Assign A New Device Owner to Devices to finalize the assignment.
Warning: Once this process is initiated, it cannot be canceled or undone.
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
Tips:
If a location's full name is truncated, hover over the name to view the full text.
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.
Placeholder Models ([Not Set]): Adds a placeholder value if the model data is missing from the MDM. These assets can be edited later without affecting nightly syncs.
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.
Verification Tab
Utilize Google login activity to verify assets for Audit Manager.
Actions:
Manual Verification: Click Start Verification to run an immediate, single-device check.
Verification Profiles: Automate verifications by creating a profile. You can run multiple profiles concurrently.
Profile Settings:
Number of days of usage to review: The login threshold required to count as "verified."
Allow Shared Devices: Verifies devices used by multiple users, provided the assigned owner meets the usage threshold.
Schedule: Set frequency (Once, Daily, Weekly, Monthly, Yearly) and a sunset date.
Select Assets: Apply filters to define which devices the profile targets.
You can edit, delete, or review the status of existing profiles at the bottom of the page.
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.
