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

# Vercel: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in Vercel. These steps are done in Vercel, not in Sprinto.

***

## Vercel access token <a href="#vercel-access-token" id="vercel-access-token"></a>

**How to tell:** Every Vercel connection uses an access token you created on your Vercel Account Tokens page and pasted into Sprinto.

**Who must do this:** The Vercel user who created the token; a team Owner for the admin-side path

**What gets removed:** The Vercel access token(s) created for Sprinto.

### Steps

1. Sign in to Vercel as the user who created the token. In the scope selector, switch to your personal account, then open **Settings** → **Account Tokens** (vercel.com/account/tokens).
2. Find the token created for Sprinto by its name and scope, and delete it from the **Account Tokens** page.
3. Or use the Vercel CLI: run `vercel tokens ls` to find the token ID, then `vercel tokens rm <token ID>`.
4. Repeat for any second token you created for Sprinto.
5. If that person has left: a team Owner selects the team, opens **Settings** → **Members**, selects the ellipses (…) next to their name and selects Remove from Team. Their tokens then lose access to the team.

### Confirm it's removed

The Account Tokens page (or `vercel tokens ls`) no longer lists a token created for Sprinto.

{% hint style="warning" %}
Removing a team member also stops every other token and integration that person set up for the team. A Full Account token keeps access to that person's own account until they delete it.
{% endhint %}

**Official guide:** [Vercel docs](https://vercel.com/kb/guide/how-do-i-use-a-vercel-api-access-token)


---

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