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

# Confluence: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                           | How to tell                                                                                                     |
| ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [Access review connection (Atlassian sign-in)](#access-review-connection-atlassian-sign-in) | Confluence was connected for user access reviews through a sign-in window.                                      |
| [Policy sync (API token)](#policy-sync-api-token)                                           | Confluence was connected as a policy source by entering a Confluence domain, an email address and an API token. |

***

## Access review connection (Atlassian sign-in) <a href="#access-review-connection-atlassian-sign-in" id="access-review-connection-atlassian-sign-in"></a>

**Who must do this:** The Atlassian user who signed in, or an Atlassian organization or site admin

**What gets removed:** The app authorization used for Confluence user access reviews.

### Steps

1. Sign in at <https://id.atlassian.com/manage-profile/apps> as the person who connected, and open the **Connected apps** tab.
2. Find the app and select **Remove access**, then confirm. The app may be listed as Sprinto or Truto.
3. If that person has left: an organization or site admin goes to admin.atlassian.com → **Apps** → select your site → **Connected apps**, selects Manage authorization for the app, then **Uninstall**. This revokes the app for every user.
4. If an admin turned on Block user apps (same Connected apps page → **Settings** tab) and the person who will reconnect isn't a site or organization admin, allow user apps again — otherwise reconnecting will fail.

### Confirm it's removed

The app no longer appears on the Connected apps tab at id.atlassian.com or in Atlassian Administration → Apps → your site → Connected apps.

{% hint style="warning" %}
If Jira was also connected for access reviews, it may use the same app; uninstalling it removes that connection too.
{% endhint %}

**Official guide:** [Atlassian docs](https://support.atlassian.com/security-and-access-policies/docs/manage-your-users-third-party-apps/)

***

## Policy sync (API token) <a href="#policy-sync-api-token" id="policy-sync-api-token"></a>

**Who must do this:** The Atlassian user who created the token, or an organization admin (Atlassian Guard) for managed accounts

**What gets removed:** The Atlassian API token Sprinto used to read your Confluence policy pages.

### Steps

1. Sign in at <https://id.atlassian.com/manage-profile/security/api-tokens> as the person who created the token (you may be asked for a one-time passcode).
2. Select **Revoke** next to the token created for Sprinto and confirm. Revoked tokens are permanently deleted.
3. If that person has left and your organization has Atlassian Guard: an organization admin goes to admin.atlassian.com → **Insights** → **API token activity** and selects Revoke for the token.
4. If you previously blocked API tokens (admin.atlassian.com → **Security** → **User security** → **Authentication policies** → **Edit**), clear Block members from creating a new or using an existing API token for the reconnecting user's policy before reconnecting with a token.

### Confirm it's removed

The token no longer appears at id.atlassian.com → Security → API tokens, or in Atlassian Administration → Insights → API token activity.

{% hint style="warning" %}
Revoking is immediate and permanent. If the same token was used for Jira or any other tool, that stops working too.
{% endhint %}

**Official guide:** [Atlassian docs](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)


---

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