Incident IQ can integrate with Securly MDM to allow device assignment changes in IIQ to be pushed into Securly MDM. This means that when a device is assigned to a user or changed from one user to another in IIQ, the assignment will update in Securly MDM.

Prerequisites

The devices must already be present in Securly MDM and IIQ with matching serial numbers
The users must be present in both Securly MDM and IIQ, matching on e-mail address

What this integration does

When a user is assigned or changed for a device in IIQ the user assignment will be sent to Securly MDM to make the same user assignment in Securly MDM. Unassigning a user

What this integration does not do

The integration does not send user assignments from Securly MDM to IIQ
The integration does not create devices in either system
The integration does not keep device inventory in sync between the two systems
The integration does not “sync” devices, assignments, or any data between the two systems. Rather it performs a one-time action, triggered by assigning a user to a device in IIQ.

Matching device inventory between systems

Because this webhook integration does not sync devices, you will need to get all of our devices listed in both systems and keep them in sync. Newly acquired devices will need to be entered into both systems, or entered in one system, then copied to the other.

There are two methods that can be used to get devices from one system to the other. The method you choose is determined by your starting point for your device list and user assignments. If your user assignments are normally made in Securly MDM, and it contains an accurate list, you can export the devices and user assignments from Securly MDM into IIQ for your starting point. If, on the other hand, you assign users to devices in IIQ and have an accurate list there, you can do the opposite.

The key in either method is to be sure to include the assigned user for each device in the export and import process. Keep in mind that the integration will only push changes from IIQ to Securly MDM, so once you have all devices and assignments in sync, you will want to make user changes in IIQ going forward. If you make a user change in Securly MDM, you would need to either manually make the same change in IIQ, or run another export/import routine from Securly to IIQ.

When deploying new devices to students, you might prefer to do so through Securly MDM, using the method of selecting a student from the list on the first run of Securly Locker while handing out the device (see the MDM User's Guide for details). In this case, your initial assignments will need to be transferred from MDM to IIQ. This can be done with the CSV export/import process.

Is there a better integration coming?

Yes (we hope)! A full integration is possible through our external API, which is already up and running and integrating with other asset management products. However, to work with IIQ, the connector on the IIQ side needs to be built by their team. They have already been provided with the technical information necessary (we built our API after consultation with them to make sure it would be easy and compatible). The connector is currently on their "customer feature request list" awaiting enough customer response to move it onto the roadmap. We strongly encourage you to reach out to your IIQ representative and stress the need and importance of a full integration with Securly MDM to overcome the limitations of the webhook method that's currently available.

Configuring the webhook integration

The integration utilizes the Webhook option in the Securly MDM’s API Connections area.

In Securly MDM

Go to Settings > API Connections
Click Add API Connection
Provide a name such as “Incident IQ webhook”
Choose any password
Click Save
The API Connection details window will appear. Close it.
Click the name of your new API connection from the table to open it
Copy the API URL and paste it into a text editor for further editing
In your text editor, add the following to the end of the URL: /devices/serial-number/{{Asset.SerialNumber}}/owner?email={{Asset.OwnerEmail}}
Your new URL should look something like this:
https://org9999.deviceconsole.securly.com/api/external/mdm/v1/devices/serial-number/{{Asset.SerialNumber}}/owner?email={{Asset.OwnerEmail}}
Click the toggle to enable the Webhook token
A window will display the webhook token. Copy the token from this window and paste it into your text editor, then close the webhook token window
In your text editor, you should now have the two pieces of information that you’ll need to copy into IIQ

In Incident IQ

We will be creating two rules in IIQ, all under Ticketing/Assets.
Rule 1: Assign user when creating an asset
Rule 2: Change/remove the user assignment when updating asset

Create rule #1: Assign user when creating an asset

This rule will trigger when creating a new asset in IIQ and assigning the user during that process, pushing the user assignment into Securly MDM. The device must already be created in Securly MDM with the same serial number.

Go to Admin > Rules
Under Ticketing, choose Assets and under Triggers choose “when Created”
Click “+CREATE NEW RULE”
Give the rule a name such as “Securly MDM assign user on device create”
Check the box for Active
Note the type is “Ticketing Assets” and the trigger is “Created”
Add Filter to trigger on Asset Type = Device
- Click Add Filter
- In the Select a filter window, enter “type” in the search box, then select Asset Type
- From the list of asset types, choose “Devices” or any other more specific asset type you may have created for your iPads.
- You should now see the new entry in the Filters section
Configure the action to perform
- Select “Web hook” from the first drop down
- Select “POST” from the request drop down
- In the URL field, enter the expanded URL that you created in your text editor earlier. It should look something like this, with the exception that your own org ID would be used instead of 9999:
  https://org9999.deviceconsole.securly.com/api/external/mdm/v1/devices/serial-number/{{Asset.SerialNumber}}/owner?email={{Asset.OwnerEmail}}
- Add two Key/Value pairs by clicking the ADD button twice to add the entry fields. Then fill them in as follows
  
  Key = Authorization
  Value = Bearer {your webhook token that you copied earlier}
  
  Key = Content-Type
  Value = application/json
  
  Your configured actions section should be similar to the following image
- Click SAVE RULE
- Your new rule should now appear in the list. You can drag and drop the rule to change the priority in the list.

Create rule #2: Change/remove the user assignment when updating asset

This rule will trigger when changing or removing a user assignment in IIQ, pushing the change into Securly MDM. The device must already be created in Securly MDM with the same serial number.

Our rule will trigger when an asset is updated with filters set for Owner Changed Today, Asset Type = Device, and perhaps other filters such as model category of computer tables.

Go to Admin > Rules
Under Ticketing, choose Assets and under Triggers choose “when Created”
Click “+CREATE NEW RULE”
Give the rule a name such as “Securly MDM change or remove user assignment”
Check the box for Active
Note the type is “Ticketing Assets” and the trigger is “Updated”
Add a filter to trigger on Asset Type = Device
- Click Add Filter
- In the Select a filter window, enter “type” in the search box, then select Asset Type
- From the list of asset types, choose “Devices” or any other more specific asset type you may have created for your iPads.
- Click SAVE SELECTION
Add a filter for "Owner Changed Today"
- Click Add Filter
- In the Select a filter window, enter “owner” in the search box, then select Owner Changed.
- Click MOVING DATE RANGES
- Click Today
- Click SAVE SELECTION
Add additional filters: you may wish to add additional filters to narrow the cases in which the webhook will trigger. For example you might limit it to only certain schools or locations where you have devices that are in Securly MDM. Based on your configuration, you might also be able to limit it to only iPad devices or a category that you use for iPads such as “Model category: Computers: Tablets” This will prevent the webhook from triggering when changing owners on other types of assets.
Configure the actions to perform. We will configure two actions. Use the "+ Add Action" button to create the second one.
Action 1: Configure a webhook using the same steps and values used for Rule #1, Assign user when creating an asset except, use a modified URL by removing everything after the word "owner". Your final URL will be similar to this:
https://org9999.deviceconsole.securly.com/api/external/mdm/v1/devices/serial-number/{{Asset.SerialNumber}}/owner
Action #2: Configure a webhook using the same steps and values used for Rule #1.

Note: It's important to enter the actions in the correct order. The first action unassigns the user and the second one assigns the new user if needed.
Your new rule should now appear in the list. You can drag and drop the rule to change the priority in the list.

How to integrate Incident IQ with Securly MDM using webhooks