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

# GitHub: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in GitHub. These steps are done in GitHub, not in Sprinto. To connect GitHub to Sprinto again later, see [Github App Integration](https://docs.sprinto.com/integrations/overview/github-integration.md), [Github + Dependabot Integration](https://docs.sprinto.com/integrations/overview/github-+-dependabot-integration.md) or [Github Issues Integration](https://docs.sprinto.com/integrations/overview/github-issues-integration.md).

## Which connection method did you use?

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

| Connection method                                                                                 | How to tell                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Legacy GitHub OAuth app](#legacy-github-oauth-app)                                               | Older connection (before the GitHub App option) where you only clicked Authorize on a GitHub OAuth screen; nothing was installed on the organization.         |
| [Sprinto GitHub App](#sprinto-github-app)                                                         | Default option: you clicked Connect with Sprinto and installed Sprinto's GitHub App on your organization (no App ID or private key was entered).              |
| [Ticketing connection (GitHub Issues)](#ticketing-connection-github-issues)                       | GitHub Issues was connected as a ticketing / change-management tool by entering a GitHub username and personal access token.                                  |
| [Your own GitHub App](#your-own-github-app)                                                       | You chose Bring Your Own GitHub App and entered an App Public Link, App ID and Private Key (github.com or a GitHub Enterprise Server URL with /github-apps/). |
| [Your own GitHub App on GHE.com (data residency)](#your-own-github-app-on-ghe-com-data-residency) | The App Public Link entered in Sprinto is on `https://<subdomain>.ghe.com/...`.                                                                               |

***

## Legacy GitHub OAuth app <a href="#legacy-github-oauth-app" id="legacy-github-oauth-app"></a>

**Who must do this:** The GitHub user who authorized the connection; organization owner for the admin path

**What gets removed:** The OAuth token Sprinto's GitHub OAuth app holds for the user who connected.

### Steps

1. The person who connected: in GitHub, click your profile picture → **Settings**.
2. In the **Integrations** section of the sidebar, click **Applications**, then the **Authorized OAuth Apps** tab.
3. Find Sprinto's app (it may be listed as Sprinto), click the … menu next to it, then click **Revoke**.
4. If that person has left: GitHub doesn't let organization owners revoke another user's OAuth grant. An owner can remove the person from the organization (**People** → select them → **Remove from organization** → **Remove members**) so the token can no longer reach organization data.

### Confirm it's removed

Sprinto's app no longer appears under Settings → Applications → Authorized OAuth Apps for that user.

**Official guide:** [GitHub docs](https://docs.github.com/en/apps/oauth-apps/using-oauth-apps/reviewing-your-authorized-oauth-apps)

***

## Sprinto GitHub App <a href="#sprinto-github-app" id="sprinto-github-app"></a>

**Who must do this:** GitHub organization owner

**What gets removed:** Sprinto's GitHub App installation on your organization, plus any personal authorization of that app.

### Steps

1. In GitHub, click your profile picture → **Your organizations**, then click **Settings** next to the organization connected to Sprinto.
2. In the sidebar, under Third-party Access, click **GitHub Apps**, then click **Configure** next to the Sprinto app. The app may be listed as Sprinto.
3. Click **Uninstall** and confirm. Repeat for every organization where you installed it.
4. If you also installed it on a personal account: profile picture → **Settings** → **Applications** → **Installed GitHub Apps** → **Configure** next to the Sprinto app → **Uninstall**.
5. Optional: the person who connected can also go to **Settings** → **Applications** → **Authorized GitHub Apps** and click **Revoke** next to the Sprinto app, if it's listed.

### Confirm it's removed

The Sprinto app no longer appears under organization Settings → GitHub Apps (or Installed GitHub Apps on the personal account).

**Official guide:** [GitHub docs](https://docs.github.com/en/apps/using-github-apps/reviewing-and-modifying-installed-github-apps)

***

## Ticketing connection (GitHub Issues) <a href="#ticketing-connection-github-issues" id="ticketing-connection-github-issues"></a>

**Who must do this:** The GitHub user who created the token; organization owner for the admin path

**What gets removed:** The personal access token created for Sprinto's GitHub Issues connection.

### Steps

1. The person who connected: in GitHub, click your profile picture → **Settings** → **Developer settings**.
2. Under Personal access tokens, click **Tokens (classic)** (or **Fine-grained tokens**) and find the token you created for Sprinto by its note or name.
3. Click **Delete** to the right of the token and confirm.
4. If that person has left and it's a fine-grained token: organization Settings → **Personal access tokens** → **Active tokens** → the token → **Revoke**. Classic tokens can't be revoked by owners; remove the person from the organization (**People** → **Remove from organization**) instead.
5. Optional: delete any saved copy of the token (password manager, notes, secrets store).

### Confirm it's removed

The token no longer appears under Developer settings → Personal access tokens (or under the org's Active tokens).

**Official guide:** [GitHub docs](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)

***

## Your own GitHub App <a href="#your-own-github-app" id="your-own-github-app"></a>

**Who must do this:** Owner of the GitHub App (organization owner or GitHub App manager; or the personal account that owns it)

**What gets removed:** The GitHub App you created for Sprinto, with all its installations and private keys.

### Steps

1. Go to the account that owns the app: profile picture → **Your organizations** → **Settings** next to the organization (for a personal app: profile picture → **Settings**).
2. In the left sidebar, click **Developer settings** → **GitHub Apps**, then select the app you created for Sprinto (setup suggested the name `sprinto-audit-app`; match the App ID you gave Sprinto).
3. In the left sidebar, click **Advanced** → **Delete GitHub App**.
4. Type the app name and click **I understand the consequences, delete this GitHub App**. This uninstalls it everywhere and removes its private keys.
5. If the app belongs to someone's personal account you can't access, an organization owner can instead go to organization Settings → **GitHub Apps** → **Configure** next to the app → **Uninstall**.
6. Optional: delete saved copies of the app's private key (`.pem` file) from downloads, password managers or secrets managers. This doesn't affect reconnecting.

### Confirm it's removed

The app no longer appears under Developer settings → GitHub Apps, and nothing is listed for it under organization Settings → GitHub Apps.

**Official guide:** [GitHub docs](https://docs.github.com/en/apps/maintaining-github-apps/deleting-a-github-app)

***

## Your own GitHub App on GHE.com (data residency) <a href="#your-own-github-app-on-ghe-com-data-residency" id="your-own-github-app-on-ghe-com-data-residency"></a>

**Who must do this:** Enterprise owner or enterprise GitHub App manager (organization owner if the app is organization-owned)

**What gets removed:** The GitHub App you created for Sprinto in your GHE.com enterprise, with all its installations and private keys.

### Steps

1. Sign in at `https://<subdomain>.ghe.com`, click your profile picture → **Your enterprise**, then click **Settings** at the top.
2. In the left sidebar, under Settings, click **GitHub Apps**, then select the app you created for Sprinto (setup suggested `sprinto-audit-app`; match the App ID you gave Sprinto).
3. Click **Advanced** → **Delete GitHub App**, type the app name and click **I understand the consequences, delete this GitHub App**.
4. If the app isn't listed there, it's owned by an organization: organization Settings → **Developer settings** → **GitHub Apps** → the app → **Advanced** → **Delete GitHub App**.
5. Optional: delete saved copies of the app's private key (`.pem` file) from downloads, password managers or secrets managers. This doesn't affect reconnecting.

### Confirm it's removed

The app no longer appears under Enterprise settings → GitHub Apps (or the organization's Developer settings → GitHub Apps).

**Official guide:** [GitHub Enterprise Cloud docs](https://docs.github.com/en/enterprise-cloud@latest/apps/maintaining-github-apps/deleting-a-github-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/github.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.
