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

# Sentry: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                         | How to tell                                                                                                              |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| [Access review connection (sign-in window)](#access-review-connection-sign-in-window)     | You signed in to Sentry and approved an integration instead of pasting a token; it shows under Settings → Integrations.  |
| [Auth token (personal or organization token)](#auth-token-personal-or-organization-token) | You followed Sprinto's help article: created a token from the auth tokens page and pasted it with the organization slug. |
| [Internal integration token](#internal-integration-token)                                 | You created an internal integration under Settings → Developer Settings and pasted its token with the organization slug. |

***

## Access review connection (sign-in window) <a href="#access-review-connection-sign-in-window" id="access-review-connection-sign-in-window"></a>

**Who must do this:** Sentry organization owner, manager or admin

**What gets removed:** The installed Sentry integration that gave Sprinto read access to your organization.

### Steps

1. Sign in to Sentry as an organization owner, manager or admin and go to **Settings** → **Integrations**.
2. Open the installed integration used for Sprinto. The app may be listed as Truto.
3. On its page, click **Uninstall**, then click **Confirm** in the "Are you sure you want to uninstall…" box.
4. The button changes to Pending Deletion while Sentry removes it (usually 10–15 minutes). Wait until it's gone before you reconnect.

### Confirm it's removed

The integration no longer appears as installed under Settings → Integrations.

**Official guide:** [Sentry docs](https://docs.sentry.io/integrations/compliance/truto/)

***

## Auth token (personal or organization token) <a href="#auth-token-personal-or-organization-token" id="auth-token-personal-or-organization-token"></a>

**Who must do this:** The user who created a personal token; an organization owner or manager for organization tokens and member removal

**What gets removed:** The Sentry auth token Sprinto used to read your organization's members.

### Steps

1. Sign in to Sentry as the person who created the token and open Settings. Under Developer Settings, select **Personal Tokens**.
2. Find the token created for Sprinto (match its last characters) and click **Revoke** on its row, then **Confirm**. The token stops working and this can't be undone.
3. If an organization token was used instead: as an organization owner or manager, go to **Settings** → **Developer Settings** → **Organization Tokens**, click **Revoke** on the token's row, then **Confirm**.
4. If the person who created a personal token has left: as an organization owner or manager, go to **Settings** → **Members**, click **Remove** on their row and confirm. Their personal tokens stop working for your organization.
5. Optional: delete any saved copies of the token (password manager, notes, secrets store).

### Confirm it's removed

The token no longer appears under Personal Tokens or Organization Tokens. Reconnecting only needs a newly created token.

**Official guide:** [Sentry docs](https://docs.sentry.io/account/auth-tokens/)

***

## Internal integration token <a href="#internal-integration-token" id="internal-integration-token"></a>

**Who must do this:** Sentry organization owner or manager

**What gets removed:** The internal integration created for Sprinto, which deletes its tokens.

### Steps

1. Sign in to Sentry as an organization owner or manager and go to **Settings** → **Developer Settings**.
2. Find the internal integration created for Sprinto (named by whoever set it up, for example Sprinto).
3. Click the trash can icon next to it.
4. Enter the confirmation text shown in the dialog and click **Confirm**.
5. Optional: delete any saved copies of the token (password manager, notes, secrets store).

### Confirm it's removed

The integration no longer appears under Settings → Developer Settings. Reconnecting only needs a new internal integration and token.

**Official guide:** [Sentry docs](https://docs.sentry.io/integrations/integration-platform/internal-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/sentry.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.
