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

# BambooHR: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                           | How to tell                                                                                                              |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| [API key (HR sync or access review)](#api-key-hr-sync-or-access-review)                     | You created an API key in BambooHR and pasted it with your company subdomain (used for HR sync, access review, or both). |
| [HR sync connection (BambooHR sign-in window)](#hr-sync-connection-bamboohr-sign-in-window) | You entered your subdomain and then signed in to BambooHR in a pop-up instead of pasting an API key.                     |

***

## API key (HR sync or access review) <a href="#api-key-hr-sync-or-access-review" id="api-key-hr-sync-or-access-review"></a>

**Who must do this:** The BambooHR user who created the key, or a BambooHR Account Owner or Admin

**What gets removed:** The BambooHR API key(s) created for Sprinto.

### Steps

1. Sign in to BambooHR as an Account Owner or Admin and go to **Settings** → **Account** → **API Keys**. This list shows every key in the account with its creator, created date and last used date.
2. Find the key created for Sprinto. Search by key name or by the person who connected Sprinto, and check the created date. If you connected both HR sync and access review, there may be two keys.
3. Delete each key from its row and confirm. Make sure it is deleted, not just marked inactive.
4. If you are the person who created the key, you can also delete it from your own list: click your name in the lower-left corner → **API Keys**.
5. Optional: if you created a custom access level or a dedicated BambooHR user only for Sprinto, remove it under **Settings** → **Access Levels**.

### Confirm it's removed

The key no longer appears under Settings → Account → API Keys (check all statuses, including inactive).

{% hint style="info" %}
The delete control on the API Keys page may be labelled differently in your account. Look for a delete or remove option next to the key.
{% endhint %}

**Official guide:** [BambooHR product update: Admin API Keys Settings](https://www.bamboohr.com/product-updates/admin-api-keys-settings)

***

## HR sync connection (BambooHR sign-in window) <a href="#hr-sync-connection-bamboohr-sign-in-window" id="hr-sync-connection-bamboohr-sign-in-window"></a>

**Who must do this:** The BambooHR user who signed in, or a BambooHR Account Owner or Admin

**What gets removed:** The API key BambooHR generated for the person who signed in, and any installed app entry for the connection.

### Steps

1. Sign in to BambooHR as an Account Owner or Admin and go to **Settings** → **Account** → **API Keys**.
2. Find the key created for the person who connected Sprinto on the date they connected (search by creator). Signing in through the pop-up makes BambooHR generate an API key for that person.
3. Delete that key from its row and confirm, so it is removed rather than marked inactive.
4. Go to **Settings** → **Apps** and check the installed apps. If the connection is listed, remove it. The app may be listed as Sprinto or Merge.
5. Optional: if you created a custom access level only for this connection, remove it under **Settings** → **Access Levels**.

### Confirm it's removed

No key created by that person for this connection remains under Settings → Account → API Keys, and the app from step 4 is no longer listed under Settings → Apps.

{% hint style="info" %}
The labels in BambooHR may differ slightly from the ones above. Look for a delete or remove option next to the app or key.
{% endhint %}

**Official guide:** [BambooHR API docs: OpenID Connect and API key](https://documentation.bamboohr.com/page/authenticate-integration)


---

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