Skip to main content
This article demonstrates how GitHub’s third-party application access policy interacts with a custom GitHub App. We’ll create a GitHub App from a personal account, attempt to install it into an organization that enforces an access policy, and follow the admin review workflow.

Step 1 — Create a GitHub App in a user account

  1. Sign in with a user account (example: the Dev2 account).
  2. From the user Settings, open Developer settings and choose Create a new GitHub App.
  3. Provide the required metadata:
    • App name
    • Description
    • Homepage URL (for example, https://example.com)
The Homepage URL is publicly visible and required when registering a GitHub App.
A dark-themed GitHub Developer Settings screenshot showing the "Create GitHub App" form. The form fields include the app name "demo-bot-dev", a description "A simple github app test", and a Homepage URL set to "https://example.com".
While registering the app you can also configure:
  • User identification settings
  • Webhooks
  • OAuth redirect URLs
If your app uses webhooks or OAuth, enable those options and supply the corresponding URLs. If not required for this test, leave them disabled or empty.

Step 2 — Choose repository permissions for the GitHub App

Grant only the minimum permissions the app needs. Examples:
Use the principle of least privilege. Only grant the permissions your app requires to reduce risk if the app is compromised.
Choose repository-level permissions carefully when the app will be installed across multiple repos. If you need scoped access, prefer installing on selected repositories rather than all repositories.
A screenshot of a GitHub settings page showing "Repository permissions" with a vertical list of permission categories (Actions, Administration, Agent secrets, Agent tasks, etc.). Most entries show "Access: No access" while Actions is set to "Read and write."

Step 3 — Register the application

After completing the form and selecting permissions, register the GitHub App. Once created, the app exposes a public installation link that can be used to install it into accounts or organizations.

Step 4 — Install the app into an organization

When you click Install App (or use the public installation link), GitHub presents install options:
  • Install on your personal account, or
  • Install on an organization where you have permission to install apps
You can opt to install on all repositories or only selected repositories. In this demo, the installer selects a single repository: game-devstudio/app-backend, then clicks Install & Request.
A dark-mode screenshot of a GitHub "Install & Request" dialog for the demo-bot-dev app, showing the option to install on only selected repositories and the selected repo "game-devstudio/app-backend" with listed permissions and an Install & Request button.

Important: organization third-party application access policy

If the target organization enforces a third-party application access policy set to Access restricted, member-initiated installs do not succeed immediately. Instead, the install becomes a pending request that requires admin approval.
If an organization uses “Access restricted” for third-party applications, any installation attempt by a member will create a pending request. Organization administrators must review and either approve or reject the request before the app is granted access.

Step 5 — Admin review and approval

Organization administrators can review pending installation requests in the organization Settings under the GitHub Applications or OAuth application policy section. In the pending installations view an admin sees:
  • App name
  • Requesting user
  • Requested repository access (which repos)
  • Permission scopes requested
The admin can approve or deny the request. If approved, the app is installed with the requested permissions and repository scope. If rejected or cancelled, the installation does not proceed.
A screenshot of a GitHub organization settings page for "game-devstudio" in dark mode, showing the Installed GitHub Apps section. It lists an installed app (Imgbot) and a pending installation request for "demo-bot-dev."
Organization admins can also:
  • Change the organization’s third-party application access policy (for example, allow installations without admin approval), or
  • Maintain a whitelist of approved apps to streamline installs.
Screenshot of a GitHub organization settings page for "game-devstudio" showing the Third-party application access policy set to "Access restricted" with a red "Remove restrictions" button and an approved "OKTA SCIM Integration."

Summary

  • Registering a GitHub App requires metadata (name, description, homepage) and selecting the minimum repository permissions needed.
  • Installing an app into an organization that enforces Access restricted will create a pending request that an admin must review and approve.
  • Organization owners can remove restrictions or maintain a whitelist to control which third-party apps are allowed.

Watch Video