> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accessowl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PagerDuty

AccessOwl integrates with PagerDuty to provision and deprovision user access in your PagerDuty account.

## Capabilities

<CardGroup cols={2}>
  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates user accounts with the specified roles/permissions during access requests.
  </Card>

  <Card title="Deprovisioning" icon="user-minus">
    AccessOwl deletes users from your PagerDuty account during access revocations.
  </Card>
</CardGroup>

## Prerequisites

* **Admin** access to your PagerDuty account, so you can invite the integration account.

## Setup

<Steps>
  <Step title="Add PagerDuty in AccessOwl">
    Either add a new application or open Applications and click the +-symbol, then continue.
  </Step>

  <Step title="Invite the integration account as Admin">
    AccessOwl shows you the integration account's email address. In PagerDuty:

    * Navigate to **People** > **Users**.
    * Click **Add Users** in the top right corner.
    * Enter the integration account's name and email address.
    * Set the base role to **Admin**.
    * Send the invite.

    <Note>
      The integration account needs the Admin base role to add and delete users on your behalf. Admin is a billable role in PagerDuty, so it will count toward your user seat usage.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="A deprovisioning request resulted in a reassignment error">
    PagerDuty does not allow deleting a user who is currently on-call on a schedule or escalation policy, or who has at least one open incident assigned to them. If a deprovisioning request results in a reassignment error, check whether the user is on an active schedule or has open incidents in PagerDuty, resolve those first, then retry the revocation in AccessOwl.
  </Accordion>
</AccordionGroup>