> 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/jamf-pro.md).

# Jamf Pro: Remove Sprinto Access

Remove the access Sprinto was given in Jamf Pro. Covers every way Sprinto can be connected to Jamf Pro and the steps to take in Jamf Pro for each.

Use this guide to remove the access you gave Sprinto in Jamf Pro. These steps are done in Jamf Pro, not in Sprinto. To connect Jamf Pro to Sprinto again later, see [Jamf Integration (Staff Device Management)](https://docs.sprinto.com/integrations/overview/jamf-integration.md), [Jamf Integration (Access Review)](https://docs.sprinto.com/integrations/overview/jamf-integration-access-review.md) or [Jamf - API Roles & Clients](https://docs.sprinto.com/integrations/overview/jamf-api-roles-and-clients.md).

## Which connection method did you use?

Sprinto can be connected to Jamf Pro in 2 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                             | How to tell                                                                                                                                          |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Jamf Pro user account (username and password)](#jamf-pro-user-account-username-and-password) | Staff device connection where you typed a Jamf domain, username and password into Sprinto (Sprinto's instructions suggested the username `sprinto`). |
| [Jamf Pro API client (client ID and secret)](#jamf-pro-api-client-client-id-and-secret)       | Access review connection, or a second Jamf device connection, where you entered a Client ID, Client Secret and Jamf URL.                             |

***

## Jamf Pro user account (username and password) <a href="#jamf-pro-user-account-username-and-password" id="jamf-pro-user-account-username-and-password"></a>

**Who must do this:** Jamf Pro administrator with privileges to delete user accounts

**What gets removed:** The Jamf Pro user account whose username and password Sprinto used.

### Steps

1. In Jamf Pro, click **Settings** in the sidebar, then in the **System** section click **User accounts & groups**.
2. Click the username of the account you created for Sprinto. It's usually `sprinto` with the full name `Sprinto Auditor`.
3. Click **Delete** in the bottom-right corner of the pane.
4. Click **Delete** in the confirmation dialog to permanently delete the account.
5. If you gave Sprinto an existing person's account instead of a dedicated one, don't delete it: change that account's password so the password Sprinto holds stops working.
6. Optional: delete any saved copies of the password (password manager entries, notes).

### Confirm it's removed

The `sprinto` account no longer appears under Settings → User accounts & groups, so the same username can be created again when you reconnect.

**Official guide:** [Jamf Pro documentation](https://learn.jamf.com/r/en-US/jamf-pro-documentation-current/Deleting_a_Jamf_Pro_User_Account)

***

## Jamf Pro API client (client ID and secret) <a href="#jamf-pro-api-client-client-id-and-secret" id="jamf-pro-api-client-client-id-and-secret"></a>

**Who must do this:** Jamf Pro administrator with privileges to manage API roles and clients

**What gets removed:** The Jamf Pro API client whose client ID and secret Sprinto used, and the API role created for it.

### Steps

1. In Jamf Pro, click **Settings** in the sidebar, then in the **System** section click **API roles and clients**.
2. Click the **API Clients** tab and open the client you created for Sprinto. Find it by its display name or by the Client ID you gave Sprinto.
3. Delete the client and confirm. If you created separate clients for access review and device sync, delete each one.
4. Click the **API Roles** tab, open the role you created for Sprinto and delete it. Skip this if another client still uses the role; Jamf Pro won't delete a role that's assigned to a client.
5. Optional: delete any saved copies of the client secret (password manager entries, notes).

### Confirm it's removed

The Sprinto client no longer appears on the API Clients tab and its role is gone from the API Roles tab.

{% hint style="info" %}
Look for **Delete** on the API client and API role pages.
{% endhint %}

**Official guide:** [Jamf Pro documentation](https://learn.jamf.com/r/en-US/jamf-pro-documentation-current/API_Roles_and_Clients)


---

# 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/jamf-pro.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.
