> 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-cloud-sonarcloud.md).

# SonarQube Cloud (SonarCloud): Remove Sprinto Access

Remove the access Sprinto was given in SonarQube Cloud (SonarCloud). Covers every way Sprinto can be connected to SonarQube Cloud (SonarCloud) and the steps to take in SonarQube Cloud (SonarCloud) for

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

***

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

**How to tell:** Only one way to connect: an API token plus organization keys pasted into Sprinto's SonarCloud form.

**Who must do this:** The user who created the token; an organization admin for scoped organization tokens and member removal

**What gets removed:** The SonarQube Cloud token Sprinto used to read your organization's issues.

### Steps

1. Sign in to SonarQube Cloud (sonarcloud.io) as the person who created the token, open the account menu (top right) and go to **My account** → **Access tokens** → **Personal Tokens**.
2. Find the token created for Sprinto and select **Revoke**.
3. If an organization admin created a scoped organization token instead (it starts with `sqco_`): open the organization → **Scoped Organization Tokens**, open the token's Actions menu, select **Revoke** and confirm.
4. If the person who created a personal token has left: as an organization admin, open the organization → **Members**, select the three-dot menu next to that person, choose **Remove** from organization's members and confirm.
5. Optional: delete any saved copies of the token (password manager, notes, secrets store).

### Confirm it's removed

The token no longer appears under My account → Access tokens (or under Scoped Organization Tokens). Reconnecting only needs a newly generated token.

**Official guide:** [Sonar docs](https://docs.sonarsource.com/sonarqube-cloud/managing-your-account/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-cloud-sonarcloud.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.
