Copy as Markdown

↵ Open esc Close

Disconnect a provider

Revoke a GitHub App connection and understand what remains.

What you'll have

The selected GitHub App disconnected, with its repositories left in GitHub.

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. Open Integrations in the organisation settings.

    Result The Forge and Lens cards show their connected accounts.

  2. On the App you intend to remove, select its Disconnect icon. Check that you chose Forge or Lens as intended.

    Result A confirmation dialog names the App you will disconnect.

  3. Confirm Disconnect.

    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.

  4. If this doesn't work

    Cancel the dialog to keep the connection. If disconnect fails, read its reason and trace identifier in Details before retrying. A GitHub uninstall delay doesn’t restore revoked local access. To reconnect after a completed disconnect, install that App again and check its GitHub account and repository selection.

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