8f964ea2cb
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Grace Park <gracepark@github.com> Co-authored-by: Steve Guntrip <12534592+stevecat@users.noreply.github.com> Co-authored-by: Robert Sese <sese@github.com> Co-authored-by: Peter Bengtsson <peterbe@github.com> Co-authored-by: Rachael Sewell <rachmari@github.com>
4.0 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| About integrations | Integrations are tools and services that connect with {% data variables.product.product_name %} to complement and extend your workflow. |
|
|
You can install integrations in your personal account or organizations you own. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization.
Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs or webhooks.
{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_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 {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}"
- "About apps"
- "User-level permissions"
- "Authorizing {% data variables.product.prodname_oauth_apps %}"
- "Authorizing {% data variables.product.prodname_github_apps %}"
- "Reviewing your authorized integrations"
You can install a preconfigured {% data variables.product.prodname_github_app %}, if the integrators or app creators have created their app with the {% data variables.product.prodname_github_app %} manifest flow. For information about how to run your {% data variables.product.prodname_github_app %} with automated configuration, contact the integrator or app creator.
You can create a {% data variables.product.prodname_github_app %} with simplified configuration if you build your app with Probot. For more information, see the Probot docs site.
Discovering integrations in {% data variables.product.prodname_marketplace %}
You can find an integration to install or publish your own integration in {% data variables.product.prodname_marketplace %}.
{% data variables.product.prodname_marketplace %} contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. For more information on finding an integration or creating your own integration, see "About {% data variables.product.prodname_marketplace %}."
Integrations purchased directly from integrators
You can also purchase some integrations directly from integrators. As an organization member, if you find a {% data variables.product.prodname_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 {% data variables.product.prodname_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.