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

# Keeper Security: Remove Sprinto Access

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

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

***

## Access review connection (SCIM API key and Node ID) <a href="#access-review-connection-scim-api-key-and-node-id" id="access-review-connection-scim-api-key-and-node-id"></a>

**How to tell:** Only method: you added a SCIM provisioning method on a Keeper node (Admin → node → Provisioning → Add Method), then pasted the generated API key and Node ID into the Keeper pop-up in Sprinto. Needs the Keeper Enterprise plan.

**Who must do this:** Keeper administrator with admin rights over the node where the SCIM method was created

**What gets removed:** The SCIM provisioning method created for Sprinto, which removes the API key (provisioning token) Sprinto holds.

### Steps

1. Sign in to the Keeper Admin Console for your region (for example `https://keepersecurity.com/console` or `https://keepersecurity.eu/console`) as a Keeper administrator.
2. Open **Admin**, select the node you created for Sprinto (the one whose Node ID you gave Sprinto), and click the **Provisioning** tab.
3. Find the SCIM method on that node, open it and delete it.
4. Or use Keeper Commander: log in as the Keeper administrator and run `scim list`. Run `scim view <SCIM endpoint ID>` to find the endpoint whose SCIM URL ends with the Node ID you gave Sprinto. Run `scim delete <SCIM endpoint ID>` and answer `y` to confirm.
5. Optional: delete any saved copies of the API key (password manager, notes). This doesn't affect reconnecting.

### Confirm it's removed

The SCIM method no longer appears on that node's Provisioning tab, and `scim list` in Keeper Commander no longer shows it.

{% hint style="warning" %}
Keeper allows one SCIM method per node. If your identity provider (for example Okta or Microsoft Entra ID) uses the same method to provision users, deleting it stops that too. Delete only the method made for Sprinto.
{% endhint %}

{% hint style="info" %}
If you don't see a delete option on the SCIM method in the node's **Provisioning** tab, use the Keeper Commander commands in step 4 instead.
{% endhint %}

**Official guides:** [Keeper docs: Commander enterprise management commands](https://docs.keeper.io/keeperpam/commander-cli/command-reference/enterprise-management-commands), [Keeper docs: Automated provisioning with SCIM](https://docs.keeper.io/enterprise-guide/user-and-team-provisioning/automated-provisioning-with-scim)


---

# 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/keeper-security.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.
