---
updatedAt: 2026-09-14T21:01:18.000Z
agentTools:
  siteIndex: https://support.pagerduty.com/llms.txt
  projectIndex: https://support.pagerduty.com/main/llms.txt
---

# Apps

Add, authorize and remove apps

Apps allow you to set up other tools to work with PagerDuty by sending data to PagerDuty or receiving data from PagerDuty. By directly integrating your existing tools, you can take advantage of PagerDuty's incident response capabilities and improve your workflows.

<Callout icon="📘" theme="info">
  ### App Development

  Apps are built by PagerDuty, partners, customers, system integrators, and the open source community. This article is a general overview of adding and managing public apps within your PagerDuty account.

  Refer to the [developer documentation](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTY3-app-overview) to learn more about creating and publishing your own app.
</Callout>

# Add Apps

Users with the appropriate permissions can add an app to their PagerDuty account following the installation instructions in the app's documentation. You can search for your desired integration's documentation by visiting the [integrations library](https://www.pagerduty.com/integrations).

<Callout icon="⚠️" theme="warn">
  ### User Permissions

  To add an app directly to a service, you must have a user role with sufficient permissions to edit the [service](https://support.pagerduty.com/main/docs/services-and-integrations).
</Callout>

## Authorize OAuth 2.0 Apps

When you authorize an app that uses OAuth 2.0, PagerDuty displays a prompt with the name of the app, your [service region](https://support.pagerduty.com/main/docs/service-regions) and user ID, and the permissions the app is requesting. Click **Authorize** to grant the app access.

<Image src="https://files.readme.io/067d46cfca8b0b2124324258fc3d9801ca872ba67ae08bada6366b0e4a9dacc6-authorize-oauth-app.webp" alt="The PagerDuty authorization prompt, showing the app name, service region, user ID, and requested permissions" align="center" width="50%" caption="Authorize app access" />

<Callout icon="📘" theme="info">
  ### Scoped OAuth Apps

  [Scoped OAuth apps](https://support.pagerduty.com/main/docs/scoped-oauth-apps) use scopes to limit the resource types an app can access, and give Admins account-wide visibility into installed apps and the tokens they hold. A public Scoped OAuth app must be installed by an Admin before you can authorize it — if the app is not installed, the authorization prompt is unavailable to you.
</Callout>

# Remove Apps

Removing an app from an account depends on how the app connects to PagerDuty. Refer to the app's [documentation](https://www.pagerduty.com/integrations) for specific instructions. General information about removing apps is in the following list:

* **Events Integrations**: [Delete the integration](https://support.pagerduty.com/main/docs/services-and-integrations#delete-an-integration) from the service.
* **Webhooks**: [Delete the extension](https://support.pagerduty.com/main/docs/extensions#delete-extensions) from the service.
* **Scoped OAuth Apps**: An Admin can revoke tokens or uninstall the app from **Integrations** :fa-arrow-right: **OAuth Apps**. For more information, visit [Scoped OAuth Apps](https://support.pagerduty.com/main/docs/scoped-oauth-apps).