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

# Asana: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in Asana. These steps are done in Asana, not in Sprinto. To connect Asana to Sprinto again later, see [Asana (Access Review) Integration](https://docs.sprinto.com/integrations/overview/asana-access-review-integration.md) or [Asana (Ticketing System) Integration](https://docs.sprinto.com/integrations/overview/asana-ticketing-system-integration.md).

## Which connection method did you use?

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

| Connection method                                                                                             | How to tell                                                                              |
| ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| [Access review or ticketing connection (Asana sign-in)](#access-review-or-ticketing-connection-asana-sign-in) | You connected Asana through a sign-in window and allowed an app access.                  |
| [Ticketing connection (personal access token)](#ticketing-connection-personal-access-token)                   | You pasted an Asana personal access token into the linking window instead of signing in. |

***

## Access review or ticketing connection (Asana sign-in) <a href="#access-review-or-ticketing-connection-asana-sign-in" id="access-review-or-ticketing-connection-asana-sign-in"></a>

**Who must do this:** The Asana user who authorized the app; a super admin for the unblock step

**What gets removed:** The app authorization that gave Sprinto access to your Asana account.

### Steps

1. As the person who connected, click your profile photo in the top bar and select **Settings**.
2. Select the **Apps** tab.
3. Find the app and deauthorize it. The app may be listed as Sprinto, Truto or Merge.
4. If a super admin blocked the app: **Admin console** → **Apps** → **Manage apps** → **Connected apps** → open the app → **Unblock** (in Require app approval mode, approve the app instead) — otherwise reconnecting will fail.

### Confirm it's removed

The app no longer appears on the Apps tab in your Asana settings.

{% hint style="warning" %}
Asana's admin console has no delete for another user's app authorization (only blocking), so the person who connected must deauthorize it.
{% endhint %}

**Official guide:** [Asana help](https://help.asana.com/s/article/apps-settings?language=en_US)

***

## Ticketing connection (personal access token) <a href="#ticketing-connection-personal-access-token" id="ticketing-connection-personal-access-token"></a>

**Who must do this:** The Asana user who created the token, or an Asana super admin

**What gets removed:** The personal access token Sprinto used.

### Steps

1. As the person who created the token, click your profile photo → **Settings** → **Apps** → **View developer console**.
2. Find the personal access token created for Sprinto and delete it.
3. If that person has left: a super admin goes to **Admin console** → **Apps** → **Manage apps**, opens the personal access tokens page and clicks Revoke for the token.
4. If a super admin turned off personal access tokens for your domain in the global app settings, turn them back on before reconnecting with a token.

### Confirm it's removed

The token no longer appears in the developer console or on the admin console's personal access tokens list.

{% hint style="info" %}
If you can't find the delete option for the token in the developer console, ask a super admin to revoke it (step 3). This also deletes the token.
{% endhint %}

**Official guide:** [Asana developer docs](https://developers.asana.com/docs/manage-and-share-your-app)


---

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