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

# Jira: Remove Sprinto Access

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

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

## Which connection method did you use?

Sprinto can be connected to Jira in 5 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)                   | Jira was connected for user access reviews through a sign-in window, separate from the Jira ticketing connection.                               |
| [API token (older connections)](#api-token-older-connections)                                                 | You pasted a Jira email address and an API token into Sprinto (older connections, before the Atlassian sign-in method).                         |
| [Sprinto Jira app (Atlassian sign-in)](#sprinto-jira-app-atlassian-sign-in)                                   | You connected Jira by signing in to Atlassian and approving Sprinto's app (the current default); no API token was pasted.                       |
| [Ticketing connection (older linking window)](#ticketing-connection-older-linking-window)                     | Jira ticketing was linked through an embedded linking window before Sprinto's own Jira app; Sprinto asks these customers to migrate to its app. |
| [Your Atlassian service account (client ID and secret)](#your-atlassian-service-account-client-id-and-secret) | You chose "Use your organization's service account" and pasted an Atlassian OAuth client ID and client secret.                                  |

***

## 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 Jira 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 Confluence 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/)

***

## API token (older connections) <a href="#api-token-older-connections" id="api-token-older-connections"></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 Jira.

### 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. Any other script or tool using the same token stops working.
{% endhint %}

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

***

## Sprinto Jira app (Atlassian sign-in) <a href="#sprinto-jira-app-atlassian-sign-in" id="sprinto-jira-app-atlassian-sign-in"></a>

**Who must do this:** The Atlassian user who approved the app, or an Atlassian organization or site admin

**What gets removed:** Sprinto's Jira app authorization for your Atlassian site.

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

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

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

***

## Ticketing connection (older linking window) <a href="#ticketing-connection-older-linking-window" id="ticketing-connection-older-linking-window"></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 by the older Jira ticketing connection.

### 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 Merge.
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.

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

***

## Your Atlassian service account (client ID and secret) <a href="#your-atlassian-service-account-client-id-and-secret" id="your-atlassian-service-account-client-id-and-secret"></a>

**Who must do this:** Atlassian organization admin

**What gets removed:** The OAuth 2.0 credential on your service account, and the service account itself if it was made only for Sprinto.

### Steps

1. Go to admin.atlassian.com → **Directory** → **Service accounts** and select the service account used for Sprinto.
2. In Credentials, select **Revoke** for the OAuth 2.0 credential whose client ID matches the one you gave Sprinto.
3. If you added this service account to the Jira admin group only for Sprinto: go to **Directory** → **Groups**, open that group, and in the **Members** tab select **Remove** for the service account.
4. If the service account was created only for Sprinto: go to **Directory** → **Service accounts**, select ••• next to it, then Delete account (this also deletes its credentials).
5. Optional: delete any saved copies of the client ID and client secret (password manager, notes). This doesn't affect reconnecting.

### Confirm it's removed

The credential no longer appears under the service account's Credentials, or the service account is gone from Directory → Service accounts.

**Official guide:** [Atlassian docs](https://support.atlassian.com/user-management/docs/create-oauth-2-0-credential-for-service-accounts/)


---

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