Revoke Access to Netlify GitHub App within Organisational Context

I’m having trouble revoking access for the Netlify GitHub App on an organisation account I’m operating.

A few things to clarify first:

  • I have my personal GitHub account
  • I have a GitHub Organisation linked to that personal account
  • I have my own Netlify account
  • The organisation has its own Netlify account

After installing the app on the GitHub organisation (from the organisation’s Netlify account), it turns out that it also exposes the specific personal repos that I previously granted it access to, from my personal Netlify account.

This, and the fact that deploying a GitHub Organisation’s private repo is only available on the Pro plan, caused me to opt for manual deployment instead.

Now, I have uninstalled the app on the organisation on GitHub, but all that did was unlink the organisation’s repo; my personal repos are still exposed and available on the list for linking to a site.

My first question is this:

Is it at all possible to only grant the Netlify GitHub App access to the organisation’s GitHub repo(s), on the organisation’s Netlify account, without exposing my repos?

And if not, how do I completely revoke access to all GitHub repos, but only on the organisation’s Netlify account?

If I have understoof this correctly, you might want to remove or configure the Netlify App here: Installed GitHub Apps. It sounds like you only configured it in the orgniazation settings, so this could be worth a shot.

Thank you for your reply, @hrishikesh.

I already had the app configured on the personal and then the organisational level, which was what caused the repos to be exposed. I have, however, uninstalled the app on the GitHub Organisation, but I can still see my personal repos from the organisation’s Netlify account, which is an unwanted behaviour.

How do I prevent the organisation’s Netlify account from accessing my personal repos?

Hi, @dannysantino. Would you please try uninstalling the GitHub app on your personal account as well? If that doesn’t resolve this issue, please let us know.