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

# Heroku: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                             | How to tell                                                                                                                                                     |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Sprinto Heroku app (team-owned authorisation)](#sprinto-heroku-app-team-owned-authorisation) | A team admin picked a team on Heroku's authorisation prompt; Sprinto then shows under that team's Settings → Team Authorizations, not under the user's account. |
| [Sprinto Heroku app (personal authorisation)](#sprinto-heroku-app-personal-authorisation)     | Default: you clicked Connect Heroku in Sprinto and authorised it without picking a team on Heroku's prompt.                                                     |

***

## Sprinto Heroku app (team-owned authorisation) <a href="#sprinto-heroku-app-team-owned-authorisation" id="sprinto-heroku-app-team-owned-authorisation"></a>

**Who must do this:** Heroku team admin

**What gets removed:** The team-owned OAuth authorisation Sprinto's app holds on your Heroku team.

### Steps

1. Sign in to the Heroku Dashboard as a team admin, open the team and go to its Settings tab.
2. In the **Team Authorizations** section, find Sprinto's entry and select the Revoke symbol on its row.
3. Select **Revoke** in the window to confirm.
4. Or use the Heroku CLI: run `heroku authorizations --team=<team>`, then `heroku authorizations:revoke <ID>` with Sprinto's ID.
5. If an admin switched off third-party OAuth access in the same Settings tab, switch it back on, otherwise reconnecting can't read team apps.

### Confirm it's removed

Team Settings → Team Authorizations (or `heroku authorizations --team=<team>`) no longer lists Sprinto.

{% hint style="warning" %}
Any team admin can revoke this, even if the admin who authorised Sprinto has left. Revoking can't be undone.
{% endhint %}

**Official guide:** [Heroku Dev Center](https://devcenter.heroku.com/articles/oauth)

***

## Sprinto Heroku app (personal authorisation) <a href="#sprinto-heroku-app-personal-authorisation" id="sprinto-heroku-app-personal-authorisation"></a>

**Who must do this:** The Heroku user who authorised Sprinto; a team admin for the admin-side path

**What gets removed:** The OAuth authorisation Sprinto's app holds on that user's Heroku account.

### Steps

1. Sign in to the Heroku Dashboard as the user who connected Sprinto and go to **Account Settings** → **Applications**.
2. Under Authorized Applications, find Sprinto's app (check its scopes) and revoke its access from that list.
3. Or use the Heroku CLI: run `heroku authorizations`, find Sprinto's entry, then run `heroku authorizations:revoke <ID>` with its ID.
4. If that person has left: a team admin runs `heroku members:remove <their email> --team <team>` (or removes them on the team's Access tab). Their authorisation then loses access to team apps.
5. If a team admin switched off third-party OAuth access in the team's Settings tab, switch it back on, otherwise reconnecting can't read team apps.

### Confirm it's removed

`heroku authorizations` (or Account Settings → Applications) no longer lists Sprinto's app.

{% hint style="warning" %}
Removing a team member also removes their access to every team app. Use it only if the person has left.
{% endhint %}

{% hint style="info" %}
If you can't find the revoke button in the dashboard, use the CLI command in step 3 instead.
{% endhint %}

**Official guide:** [Heroku Dev Center](https://devcenter.heroku.com/articles/oauth)


---

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