> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/remove-integration-access/pagerduty.md).

# PagerDuty: Remove Sprinto Access

Remove the access Sprinto was given in PagerDuty. Covers every way Sprinto can be connected to PagerDuty and the steps to take in PagerDuty for each.

Use this guide to remove the access you gave Sprinto in PagerDuty. These steps are done in PagerDuty, not in Sprinto. To connect PagerDuty to Sprinto again later, see [PagerDuty Integration](https://docs.sprinto.com/integrations/overview/pagerduty-integration.md).

## Which connection method did you use?

Sprinto can be connected to PagerDuty in 2 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                         | How to tell                                                                                             |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| [Access review connection (sign-in window)](#access-review-connection-sign-in-window)     | You connected PagerDuty for access review in Sprinto and approved access in a PagerDuty sign-in pop-up. |
| [Sprinto PagerDuty app (incident management)](#sprinto-pagerduty-app-incident-management) | You clicked Connect PagerDuty in Sprinto's incident management setup and approved access in PagerDuty.  |

***

## Access review connection (sign-in window) <a href="#access-review-connection-sign-in-window" id="access-review-connection-sign-in-window"></a>

**Who must do this:** PagerDuty Admin or Account Owner

**What gets removed:** The OAuth app used for the access review connection and every token it holds in your account.

### Steps

1. Sign in to PagerDuty as an Admin or the Account Owner and go to **Integrations** → **OAuth Apps**.
2. Select the app used for the access review connection. The app may be listed as Sprinto or Truto.
3. Click **Uninstall**. This revokes all user tokens for the app, including tokens from people who have left.
4. If your account has no OAuth Apps page yet: go to **People** → **Users**, select the person who connected, open User Settings, click Change Password…, enter your password, set a new one and click **Save**. This revokes that user's OAuth tokens.
5. If that person has left, you can instead delete them: **People** → **Users** → their Name → **Delete User**, then confirm.

### Confirm it's removed

The app no longer appears under Integrations → OAuth Apps. To reconnect later, an Admin must connect (or install the app first).

{% hint style="warning" %}
If both PagerDuty connections show the same app, uninstalling it also stops the incident management connection. Step 4 revokes all of that user's OAuth tokens, so other apps they connected need to be reconnected.
{% endhint %}

**Official guide:** [PagerDuty docs](https://docs.pagerduty.com/integrations/apps/scoped-oauth-apps)

***

## Sprinto PagerDuty app (incident management) <a href="#sprinto-pagerduty-app-incident-management" id="sprinto-pagerduty-app-incident-management"></a>

**Who must do this:** PagerDuty Admin or Account Owner

**What gets removed:** Sprinto's PagerDuty OAuth app and every token it holds in your account.

### Steps

1. Sign in to PagerDuty as an Admin or the Account Owner and go to **Integrations** → **OAuth Apps**.
2. Select the app used for Sprinto incident management. The app may be listed as Sprinto.
3. Click **Uninstall**. This revokes all user tokens for the app, including tokens from people who have left.
4. If your account has no OAuth Apps page yet: go to **People** → **Users**, select the person who connected, open User Settings, click Change Password…, enter your password, set a new one and click **Save**. This revokes that user's OAuth tokens.
5. If that person has left, you can instead delete them: **People** → **Users** → their Name → **Delete User**, then confirm.

### Confirm it's removed

The app no longer appears under Integrations → OAuth Apps. To reconnect later, an Admin must connect (or install the app first), because uninstalled public apps can't be authorized until an Admin installs them.

{% hint style="warning" %}
Step 4 signs that user out of PagerDuty and revokes all their OAuth tokens, so other apps they connected (for example the mobile app or Slack) need to be reconnected. Use it only if the OAuth Apps page isn't available.
{% endhint %}

**Official guide:** [PagerDuty docs](https://docs.pagerduty.com/integrations/apps/scoped-oauth-apps)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/integrations/remove-integration-access/pagerduty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
