You can install integrations in your personal account or organizations you own. You can also install GitHub Apps from a third-party in a specific repository where you have admin permissions or which is owned by your organization.
Integrations can be GitHub Apps, OAuth Apps, or anything that utilizes GitHub APIs or webhooks.
GitHub Apps offer granular permissions and request access to only what the app needs. GitHub Apps also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app.
For more information, see:
- "Differences between GitHub Apps and OAuth Apps"
- "About apps"
- "User-level permissions"
- "Authorizing OAuth Apps"
- "Reviewing your authorized integrations"
You can install a preconfigured GitHub App, if the integrators or app creators have created their app with the GitHub App manifest flow. For information about how to run your GitHub App with automated configuration, contact the integrator or app creator.
You can create a GitHub App with simplified configuration if you build your app with Probot. For more information, see the Probot docs site.
You can find an integration to install or publish your own integration in GitHub Marketplace.
You can also purchase some integrations directly from integrators. As an organization member, if you find a GitHub App that you'd like to use, you can request that an organization approve and install the app for the organization.
If you have admin permissions for all organization-owned repositories the app is installed on, you can install GitHub Apps with repository-level permissions without having to ask an organization owner to approve the app. When an integrator changes an app's permissions, if the permissions are for a repository only, organization owners and people with admin permissions to a repository with that app installed can review and accept the new permissions.