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

# Snyk: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                           | How to tell                                                                                                                              |
| --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| [Access review connection (API token)](#access-review-connection-api-token) | Connected from Sprinto's access review integrations (Snyk user list) by pasting a Snyk token in a sign-in window; needs Snyk Enterprise. |
| [Vulnerability connection (API token)](#vulnerability-connection-api-token) | Connected from the Snyk tile under vulnerability scanners in Sprinto by pasting an API token and choosing a region.                      |

***

## Access review connection (API token) <a href="#access-review-connection-api-token" id="access-review-connection-api-token"></a>

**Who must do this:** The Snyk user whose token was used (an Org Admin); Org Admin or Group Admin for service accounts

**What gets removed:** The Snyk token used to read your organization's members and roles.

### Steps

1. Sign in to Snyk as the person who connected and open your account settings.
2. On the **General** page, next to your API token click **Revoke & Regenerate**. Snyk has no delete for this key; resetting permanently invalidates the key Sprinto holds.
3. If you used a personal access token: open your account settings → **Personal access tokens** tab and click **Revoke** next to the token.
4. If you used a service account token: open the Organization (or Group) → **Settings** → **Service accounts**, click **Delete** next to the service account created for Sprinto, then click **OK**.
5. If the person who connected with a personal token has left: an Org Admin opens the Organization → **Members**, clicks the trash icon next to that user and clicks Delete member from your Organization.
6. Optional: delete any saved copies of the token.

### Confirm it's removed

The old token no longer works: it was regenerated in General settings, is gone from Personal access tokens, or its service account is deleted.

{% hint style="warning" %}
Revoke & Regenerate breaks every other tool (CLI, IDE, CI, other Sprinto Snyk connection) that uses the same personal API token.
{% endhint %}

**Official guide:** [Snyk docs](https://docs.snyk.io/developer-tools/snyk-api/authentication-for-api/revoke-and-regenerate-a-snyk-api-token)

***

## Vulnerability connection (API token) <a href="#vulnerability-connection-api-token" id="vulnerability-connection-api-token"></a>

**Who must do this:** Snyk Org Admin or Group Admin (service accounts); the token owner for personal tokens

**What gets removed:** The Snyk service account or personal token Sprinto used to read projects and issues.

### Steps

1. Sign in to Snyk at your region's address (for example app.snyk.io or app.eu.snyk.io).
2. If you used a service account token: open the Organization (or Group) → **Settings** → **Service accounts**, click **Delete** next to the service account created for Sprinto, then click **OK**.
3. If you used a personal access token: open your account settings → **Personal access tokens** tab and click **Revoke** next to the token.
4. If you used your personal API token (account settings → **General**): click **Revoke & Regenerate**. Snyk has no delete for this key; resetting permanently invalidates the key Sprinto holds.
5. If the person who connected with a personal token has left: an Org Admin opens the Organization → **Members**, clicks the trash icon next to that user and clicks Delete member from your Organization.
6. Optional: delete any saved copies of the token.

### Confirm it's removed

The service account no longer appears under Settings → Service accounts (or the token is gone from Personal access tokens / replaced in General settings).

{% hint style="warning" %}
Revoke & Regenerate on a personal API token breaks every other tool (CLI, IDE, CI) that uses that token.
{% endhint %}

**Official guide:** [Snyk docs](https://docs.snyk.io/platform-administration/service-accounts/service-accounts)


---

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