Org owners can install directly. Repo admins can install apps that don't ask for org-level or repository-administration permissions, and only if the org hasn't turned that off. Everyone else gets a Request button instead, which sends it to the owners for approval.

The flow itself:

1. Go to the app's page, https://github.com/apps/<APP-SLUG>, or straight to https://github.com/apps/<APP-SLUG>/installations/new.
2. Pick the org from the account list (easy to fat-finger your personal account here).
3. Choose All repositories or Only select repositories.
4. Read the permissions it's asking for, then hit Install — or Request, if you're not an owner.
5. If it became a request, an owner clears it under Org → Settings → Third-party Access → GitHub Apps.

Same place to change repo access later: Configure next to the app → Repository access → Save. Suspend cuts its access temporarily, Uninstall removes it.

To see what's already installed:

gh api /orgs/YOUR-ORG/installations \
  --jq '.installations[] | {app_slug, target_type, repository_selection}'

{"app_slug":"renovate","target_type":"Organization","repository_selection":"selected"}

You have to be an owner for that call. Worth knowing: it 404s rather than 403s when your token is short on scopes, which is confusing the first time. The headers tell you what it wanted:

X-Accepted-Oauth-Scopes: admin:org, read:org, write:org
X-Oauth-Scopes: repo, workflow

gh auth refresh -h github.com -s read:org fixes that.

A few things that catch people out:

• Only select repositories doesn't pick up repos you create later — you have to add them by hand. The exception is repos the app itself creates.
• If you see Request where you expected Install, an owner has restricted it under Settings → Member privileges → Access ("App access requests", and the "Allow repository admins to install GitHub Apps for their repositories" checkbox).
• If the org uses an IP allow list, switch on Enable IP allow list configuration for installed GitHub Apps first. Otherwise the install looks fine and the app just fails with connection errors afterwards.
• GET /user/installations won't work with a classic PAT — that one needs a user-to-server token from the app's own OAuth flow.

Docs: installing a GitHub App from a third party and reviewing and modifying installed GitHub Apps.

I recently installed a GitHub App on an organisation, and one thing I learned is to double-check the permissions before installing. Also, make sure you're signed in with an account that has Organization Owner access, otherwise the installation can fail or some options won't appear.

If everything looks correct but you're still having trouble, could you share the exact error or where the installation gets stuck? That would make it much easier for others to help.

Hope you get it working soon!

GitHub Apps are much better than the old OAuth apps because they offer granular permissions, but some app developers are lazy and request "Read/Write" access to everything by default. If an app only needs to manage Issues or Projects, it shouldn't be asking for full write access to your source code. Also, check your Organization Settings under "Third-party access" — if your org has OAuth app access restrictions enabled (especially if you use SAML SSO), you may need to specifically whitelist the app or authorize your SSO session during the install. Vegastars Casino may appeal to fans of a familiar Vegas-style atmosphere. The more important question is whether the lobby offers enough organisation to keep that large-scale https://vegastarscasino.co.com/ presentation from becoming cluttered.

Hi Soumitra,

Even though I'm a bit late and the other users answers are great and very helpful, I will give you my take on it and hopefully that will be somewhat helpful to you. Installing and managing GitHub Apps at the organization level is straightforward,once you know the permission rules and common pitfalls. Here is a comprehensive guide covering the process, best practices, and edge cases:

1)Permission Requirements & Approval Flow:
Organization Owners: Can install any app directly.

Repository Admins: Can install apps only if the app doesn't request organization-level or repository-administration permissions, and provided the org hasn't disabled this setting (Settings → Member privileges).

Members / Non-Owners: Will see a "Request" button instead of "Install". This sends an approval request to Org Owners, accessible under Org Settings → Third-party Access → GitHub Apps.

2. Step by Step Installation Process:
   Navigate to the App: Go to the app's Marketplace page or installation URL (https://github.com/apps/).

Select Account: Choose your Organization (be careful not to accidentally select your personal account).
Repository Scope:
Only select repositories (Recommended): Limits access strictly to selected repos. (Note: Newly created repositories won't automatically be added later unless created by the app itself, you willl need to add them manually via app settings).

All repositories: Grants access across the entire organization.

Review Permissions & Authorize: Carefully inspect requested scopes and click Install (or Request).

3. Critical Pre Checks & Pitfalls
   IP Allow Lists: If your organization uses an IP Allow List, enable "Enable IP allow list configuration for installed GitHub Apps" before installing. Otherwise, the installation will succeed, but the app's webhooks/API requests will fail silently.

SAML SSO Enforcement: Ensure your active session is authorized with your organization's SAML SSO before proceeding.

Audit Requested Scopes: GitHub Apps offer granular permissions. Be cautious if an app requests full Read/Write access to source code or Administration if it only needs access to Issues or Discussions.

4.)Pro-->Tip: Managing & Auditing via GitHub CLI
If you are an Owner and want to quickly inspect installed apps and their scope across your organization via the terminal:

go to your terminal (Bash) and type:

gh api /orgs/YOUR-ORG/installations
--jq '.installations[] | {app_slug, target_type, repository_selection}'
(If this command returns a 404 error instead of data, refresh your token scopes using gh auth refresh -h github.com -s read:org).

Hopefuly, this helps you set up your GitHub App smoothly! Let us know if you run into any issues during the process.Send me your opinion on it, I'll be waiting!!!