Managing Or Disconnecting Github Oauth Connections E3dc3b

The option to disconnect a GitHub account may be missing from Project or Organization settings, or permission errors may be displayed when trying to modify organization-level integrations. This happens because the GitHub integration is managed at three distinct levels — Account, Organization, and Project — and the underlying OAuth grant lives at the Account level.

Where the GitHub connection is configured

1. Account preferences

In Account Preferences you authorize the GitHub OAuth app so Supabase can read your repositories. From here you can re-authenticate or remove the connection entirely.

2. Organization integration settings

In Organization Integration Settings you can see every project in the organization that is connected to a GitHub repository. From here you can:

• Open Configure connection to jump to the Project integration settings.
• Delete a connection to remove the link between a project and its GitHub repository. This does not revoke the underlying OAuth grant on the account level.

If your role only grants access to a subset of projects in the organization, the GitHub and Vercel sections of this page can return a permission error. See Access Control — organization integration permissions for the required permissions.

3. Project integration settings

Project-level settings let you sync preview branches with a chosen GitHub branch, keep the production branch in sync, and automatically create a preview branch for every pull request.

How to update or remove the connection

1. Go to Account Preferences.
2. Find the GitHub integration section.
3. Click Manage, then Remove connection.
4. To link a different GitHub account or change the granted scope, re-initiate the GitHub connection flow from the project or organization where you want the new link to apply.

Related guides

• Access Control — organization integration permissions
• Branching