Overview
Seamlessly add assets to allwhere and synchronize device specifications by connecting your Iru (Kandji) to allwhere.
Key Features
1. Continuously share and update data
- Iru (Kandji) will sync with allwhere once a day
2. Create new assets in allwhere from Iru (Kandji)
- Minimum requirements for a new asset to be created in allwhere
- allwhere can determine the asset type based on model and OS (laptop, mobile, tablet etc)
- The asset has a serial number
- Determining status and assignee information for new assets
- The asset status for any new asset added to allwhere will be allocated
- If the asset in Iru (Kandji) contains an email address that allwhere can match with an existing user, the existing user will be linked as the assignee on that asset
- If the asset in Iru (Kandji) contains an email address, first name and last name, and the assignee does not exist in allwhere, a new employee will be created and linked to the new asset
- If the asset in Iru (Kandji) contains no email address, allwhere will create the asset without an assignee in the allocated status
3. Update existing allwhere asset data with device info from Iru (Kandji)
- Serial number will be the unique identifier. So, if allwhere finds a matching serial number, then we will update the existing asset record so that the device hardware information from Iru (Kandji) will override asset data in allwhere.
- Iru (Kandji) will become the source of truth for the following fields:
- color,
- display size,
- IMEI number,
- keyboard language,
- make,
- memory,
- model,
- model number,
- operating system,
- processor,
- processor frequency,
- release date,
- storage,
- storage type,
- Iru (Kandji) ID
-
Coming soon: Wherever possible, model information will be parsed into the appropriate fields
-
Example
Iru (Kandji) Model Field allwhere fields MacBook Pro (13-inch, 2018) Model: MacBook Pro
Display Size: 13"
Release Date: 2018
-
- Iru (Kandji) will become the source of truth for the following fields:
- By default, allwhere will remain the source of truth for assignee, location, status and condition for existing assets. You can optionally enable MDM-Driven Assignee Updates to let Iru (Kandji) update the allwhere assignee during sync
4. Create new employees in allwhere from Iru (Kandji)
- If your Iru (Kandji) instance includes reference to assignee that does not already exist in allwhere, we will create a new employee and assign the asset to that employee
- Minimum fields required are First Name, Last Name and at least one email address
-
WARNING: If your allwhere instance currently contains a list of employees that only has personal emails and your Iru (Kandji) instance contains a list of assignees that only has work emails, allwhere will create new employee records for all of your Iru (Kandji) assignees. This may result in duplicate employee records being created in allwhere.
- We recommend you ensure all employees in allwhere have work emails associated with them prior to connecting Iru (Kandji) to avoid creating duplicate employee records in allwhere.
5. New fields added to the allwhere backend (coming soon)
- The following fields will not be immediately accessible in the UI but will be available to allwhere operations team to improve our ability to service your devices:
- Recovery key, activation lock enabled (y/n), recovery lock enabled (y/n), Apple Care ID
Ready to get started?
Click here for a detailed guide on how to set up your integration