See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Disconnect a provider

Revoke a GitHub App connection and understand what remains.

<!-- https://docs.crusible.dev/admin/disconnect-a-provider/ · doctype: how-to · role: admin · reviewed: pending human review -->


Disconnect each GitHub App separately.
You need permission to manage integrations.
Before disconnecting, tell people relying on its repositories that application access will stop.


1. <p>Open <strong>Integrations</strong> in the organisation settings.</p>
 (Result: The Forge and Lens cards show their connected accounts.)


1. <p>On the App you intend to remove, select its <strong>Disconnect</strong> icon.
Check that you chose Forge or Lens as intended.</p>
 (Result: A confirmation dialog names the App you will disconnect.)


1. <p>Confirm <strong>Disconnect</strong>.</p>
 (Result: The application revokes its local bindings for that App and asks GitHub to uninstall it. Its card offers installation again after the list refreshes.)


- **If this doesn't work:** <p>Cancel the dialog to keep the connection.
If disconnect fails, read its reason and trace identifier in <strong>Details</strong> before retrying.
A GitHub uninstall delay doesn&rsquo;t restore revoked local access.
To reconnect after a completed disconnect, install that App again and check its GitHub account and repository selection.</p>





GitHub keeps the repositories and pull requests.
Disconnect removes access; it doesn't promise to erase records already held in the application.

- [Connect a provider](https://docs.crusible.dev/admin/connect-a-provider/) — Install the GitHub Forge and Lens Apps and check their connection states.- [GitHub](https://docs.crusible.dev/reference/providers/github/) — GitHub App installation, access, records, refresh and disconnect.