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

# SpringVerify: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                       | How to tell                                                                         |
| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| [SpringVerify India (API token)](#springverify-india-api-token)                         | You chose 'Use SpringVerify India' in Sprinto and pasted an API token.              |
| [SpringVerify US (admin email and password)](#springverify-us-admin-email-and-password) | You chose 'Use SpringVerify US' in Sprinto and entered an admin email and password. |

***

## SpringVerify India (API token) <a href="#springverify-india-api-token" id="springverify-india-api-token"></a>

**Who must do this:** SpringVerify company Admin (Settings is Admin-only)

**What gets removed:** The API token you generated for Sprinto is deleted, so the copy Sprinto holds stops working.

### Steps

1. Sign in to the SpringVerify portal (portal.in.springverify.com) as an Admin.
2. Click the **Profile** button at the top-right and go to Settings.
3. Open the **Settings** tab and click the API subsection.
4. Find the token you generated for Sprinto by its name and delete it from its row. Any Admin can do this, even if the person who made it has left.
5. If you can't find a delete option, ask SpringVerify support (<cs@springverify.com>) to revoke the token.

### Confirm it's removed

The Sprinto token no longer appears under Settings → API in the SpringVerify portal.

{% hint style="info" %}
Look for a delete or revoke option next to the token under **Settings → API**.
{% endhint %}

**Official guide:** [SpringVerify India API docs](https://documenter.getpostman.com/view/3927563/2s8YswRX6z)

***

## SpringVerify US (admin email and password) <a href="#springverify-us-admin-email-and-password" id="springverify-us-admin-email-and-password"></a>

**Who must do this:** SpringVerify company Admin

**What gets removed:** The login Sprinto used is deleted (or its password is changed), so the credentials Sprinto holds stop working.

### Steps

1. Sign in to SpringVerify US as a company Admin.
2. If the login you gave Sprinto belongs to a user made only for Sprinto: go to My Team, click the **Delete** icon next to that user, and confirm in the pop-up.
3. If it's a real person's login: have that person change their SpringVerify password. This permanently invalidates the password Sprinto holds.
4. If that person has left: delete their user from My Team (**Delete icon** → confirm).

### Confirm it's removed

The Sprinto-only user no longer appears under My Team, or the old password no longer signs in.

{% hint style="warning" %}
SpringVerify US has no separate key for this connection, so Sprinto used an admin's own login. Changing that person's password also affects any other tool that signs in with the same login.
{% endhint %}

{% hint style="info" %}
The options in SpringVerify US may be labelled differently from the ones above.
{% endhint %}

**Official guide:** [SpringVerify help](https://support.springworks.in/portal/en/kb/articles/how-do-i-add-users-from-my-end-to-manage-the-portal)


---

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