> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/remove-integration-access/iru-kandji.md).

# Iru (Kandji): Remove Sprinto Access

Remove the access Sprinto was given in Iru (Kandji). Covers every way Sprinto can be connected to Iru (Kandji) and the steps to take in Iru (Kandji) for each.

Use this guide to remove the access you gave Sprinto in Iru (Kandji). These steps are done in Iru (Kandji), not in Sprinto. To connect Iru (Kandji) to Sprinto again later, see [Iru (Kandji) Integration](https://docs.sprinto.com/integrations/overview/kandji-integration.md).

***

## API token <a href="#api-token" id="api-token"></a>

**How to tell:** You pasted an Iru (Kandji) API token and API URL into Sprinto, for staff device sync or access review.

**Who must do this:** Iru Endpoint administrator who can open Access

**What gets removed:** The Iru (formerly Kandji) API token that Sprinto used.

### Steps

1. In the Iru Endpoint web app (formerly Kandji), select the Account Menu Button in the sidebar, then select **Access**. Older Kandji tenants show this as **Settings** → **Access**.
2. Select the **API tokens** tab and find the token you created for Sprinto. It's usually named `Sprinto Access`.
3. Select the vertical ellipsis next to the token, then select **Revoke**.
4. Enter the token name exactly as shown in the prompt, then select **Revoke** to confirm. The token disappears from the list.
5. If you created a second token for Sprinto (one for device sync and one for access review), repeat steps 3–4 for it.
6. Optional: delete any saved copies of the token (password manager entries, notes).

### Confirm it's removed

No Sprinto token is listed on the API tokens tab in Access.

**Official guide:** [Iru docs](https://docs.iru.com/en/endpoint/api/iru-api-overview)


---

# 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.sprinto.com/integrations/remove-integration-access/iru-kandji.md?ask=<question>&goal=<user_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.
