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

# Jenkins: Remove Sprinto Access

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

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

***

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

**How to tell:** You entered a Jenkins username, API Token and Jenkins URL in Sprinto.

**Who must do this:** The Jenkins user whose token was used; Jenkins administrator (Overall/Administer) for the admin path

**What gets removed:** The Jenkins API token Sprinto uses (and the Jenkins user, if it was created only for Sprinto).

### Steps

1. Sign in to Jenkins as the user whose username you gave Sprinto, click your name (top right) → **Security** (shortcut: `<your Jenkins URL>/me/security`).
2. Under **API Token** → **Current token(s)**, find the token you created for Sprinto (by its name or last-use date) and click its trash icon (Revoke). In the **Revoke token** box, click **Revoke**. Apps using it can no longer connect; there's nothing else to save.
3. If that user has left, a Jenkins administrator can go to **Manage Jenkins** → **Users**, open that user, select **Security** and revoke the token the same way.
4. If you created a Jenkins user only for Sprinto, delete it: **Manage Jenkins** → **Users** → trash icon next to the user → confirm. Deleting the user also invalidates all its tokens.
5. Optional: delete any saved copy of the token.

### Confirm it's removed

The Sprinto token no longer appears under the user's Security → API Token list (or the dedicated user no longer appears under Manage Jenkins → Users).

**Official guide:** [Jenkins docs](https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/)


---

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