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

# Tailscale: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                 | How to tell                                                                                    |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| [API access token](#api-access-token)                             | You generated an API access token under Settings → Keys and entered it with your tailnet name. |
| [OAuth client (trust credential)](#oauth-client-trust-credential) | You created an OAuth client under Trust credentials and entered its client ID and secret.      |

***

## API access token <a href="#api-access-token" id="api-access-token"></a>

**Who must do this:** The Tailscale user who generated the token (Owner, Admin, IT admin or Network admin)

**What gets removed:** The API access token Sprinto used is revoked.

### Steps

1. Sign in to the Tailscale admin console as the person who generated the token and open **Settings** → **Keys**.
2. In the **API access tokens** section, find the token you created for Sprinto (check its description and creation date).
3. Select **Revoke** next to the token and confirm.
4. If the person who generated it has left: an Owner or Admin deletes that user on the **Users** page — Tailscale automatically revokes a deleted user's API access tokens.
5. Optional: Delete any saved copies of the token (password manager, notes). This doesn't affect reconnecting.

### Confirm it's removed

The token shows as revoked (or is no longer listed) in the API access tokens section of the Keys page.

**Official guide:** [Tailscale docs](https://tailscale.com/docs/reference/key-secret-management)

***

## OAuth client (trust credential) <a href="#oauth-client-trust-credential" id="oauth-client-trust-credential"></a>

**Who must do this:** Tailscale Owner, Admin, Network admin or IT admin

**What gets removed:** The OAuth client created for Sprinto is revoked, along with every access token it issued.

### Steps

1. Sign in to the Tailscale admin console and open the **Trust credentials** page.
2. Find the OAuth client you created for Sprinto (match its client ID). Admins can see every OAuth client, whoever created it.
3. Select **Revoke**.
4. Select **Revoke** again to confirm.
5. Optional: Delete any saved copies of the client secret (password manager, notes). This doesn't affect reconnecting.

### Confirm it's removed

The OAuth client no longer appears as active on the Trust credentials page.

**Official guide:** [Tailscale docs](https://tailscale.com/docs/reference/trust-credentials)


---

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