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

# SonarQube Server: Remove Sprinto Access

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

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

***

## User token <a href="#user-token" id="user-token"></a>

**How to tell:** Only one way to connect: a user token and your SonarQube URL pasted into Sprinto's SonarQube form.

**Who must do this:** The user who created the token, or a System Administrator (Administer System permission)

**What gets removed:** The SonarQube Server user token named Sprinto.

### Steps

1. Sign in to your SonarQube Server instance as the user who created the token and go to the account menu → **My Account** → **Security**.
2. Find the token named `Sprinto` (the name Sprinto's setup suggested) and select **Revoke** next to it.
3. If that user has left: as a System Administrator, go to **Administration** → **Security** → **Users** and find the user.
4. In the user's Tokens column, select the three-dot menu, then select **Revoke** in the Actions column of the `Sprinto` token.
5. Optional: delete any saved copies of the token.

### Confirm it's removed

The Sprinto token no longer appears under My Account → Security (or in the user's Tokens dialog).

**Official guide:** [Sonar docs](https://docs.sonarsource.com/sonarqube-server/user-guide/managing-tokens)


---

# 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/sonarqube-server.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.
