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

# Checkr: Remove Sprinto Access

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

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

***

## Sprinto Checkr app (Checkr sign-in) <a href="#sprinto-checkr-app-checkr-sign-in" id="sprinto-checkr-app-checkr-sign-in"></a>

**How to tell:** Only method: you clicked Connect in Sprinto and signed in to Checkr to authorize Sprinto.

**Who must do this:** Checkr account Admin

**What gets removed:** Sprinto's authorization to your Checkr account is removed, which invalidates the token Sprinto holds.

### Steps

1. Sign in to the Checkr Dashboard as an account Admin.
2. Go to **Account Settings** → **Integrations**.
3. Find the app Sprinto used. The app may be listed as Sprinto.
4. Click **Turn off** next to it to disconnect it. This deauthorizes Sprinto's access for the whole Checkr account.
5. Checkr connects at account level, so any Checkr Admin can do this even if the person who connected has left.

### Confirm it's removed

Sprinto no longer shows as connected under Account Settings → Integrations in the Checkr Dashboard.

{% hint style="info" %}
If the labels in your Checkr Dashboard differ, look for the Sprinto integration under your account settings and turn it off or deauthorize it.
{% endhint %}

**Official guide:** [Checkr partner docs](https://docs.checkr.com/partners/)


---

# 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/checkr.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.
