> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-mdm/iru-integration.md).
# Connect Iru (formerly Kandji)
Connect Iru, formerly Kandji, to Siit: create an API token with device list, details and action permissions in Iru, then enter it with your API URL in Siit
#### Part 1: Configure Iru API Token
***
* Log in to your **Iru dashboard**.
* Go to **Settings → Access**.
* Next to Admin and authentication, click on **API tokens**
**“ + Add token”**
* Enter a name for the new token (e.g., **“Siit”**) and click **“Create”**.
* Copy the **API Token** and save it somewhere safe.
* Click **“Next”**.
* In the **Manage Permissions** modal, click **“Skip”**.
* Copy the **Organization’s API URL** (you’ll need it later).
* Click the **three dots (•••) → View → Configure Permissions**.
* Enable the following permissions for Siit:
* **Device list** (required)
* **Device details** (required)
* Clear device passcode
* Lock device
* Erase device
* Restart device
* Shutdown device
* Account unlock
* Click **“Save”**.
#### Part 2: Enable Iru Integration in Siit
***
1. Log in to your **Siit Admin Dashboard**:
2. Click the **Settings (⚙️) icon** in the top-right corner.
3. Find the **Iru** integration and click **“Connect Now”**.
4. Enter the **API URL** and **API Token** you copied earlier.
5. Click **“Configure”**.
🎉 **Done!** Your Iru integration is now active in Siit, and your devices will sync automatically.
#### What you'll see synced automatically
* **Office location**: Siit now maps each device's office location straight from Iru, instead of leaving it blank for you to fill in by hand.
* **Status follows the owner**: if you assign an owner to a device marked "Spare," Siit switches it to "In service" for you, unless you changed the status yourself in that same edit.
ℹ️ This applies automatically once your integration is connected, no extra setup needed.
#### Can I run Iru actions in a workflow?
Yes. Workflows can lock, erase, restart or shut down a device, clear its passcode, unlock a user account, and send the recovery key or Recovery Lock password privately to the requester. Erasing a device asks for an approval first. Each action needs the matching permission in Part 1. See [Run device actions from a workflow](/guides/workflows/run-device-actions-from-a-workflow.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.siit.io/guides/integrations/integrations-mdm/iru-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
