> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/pagerduty-integration-setup.md).

# PagerDuty Integration Setup

### Getting Started

Use this guide to connect PagerDuty to your BalkanID tenant. You will need an API key from PagerDuty and access to the Integrations section in BalkanID.

Once connected, BalkanID syncs your PagerDuty users, their base roles, and your teams, along with the access between them.

BalkanID recommends creating the API key from a service account rather than a personal or employee-named account.

#### Requirements:

Before you begin, collect the following value from PagerDuty:

* **Access Token**

### Configure PagerDuty within your BalkanID tenant

1. To find the Access Token, sign in to PagerDuty as a user with the **Global Admin** or **Account Owner** role.
2. Navigate to **Integrations > Developer Tools > API Access Keys**.
3. Click **Create New API Key**, enter a description, and tick **Read-only API Key**. BalkanID only reads from PagerDuty, so a read-only key is sufficient.
4. Click **Create Key** and copy the key immediately. PagerDuty displays the full key only once; afterwards only the last four characters are shown.
5. In BalkanID, go to **Integrations** and click **Add integration**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Ff67UsycSGVVYbDGKzze3%2Fpagerduty-add-integration.png?alt=media" alt="The BalkanID Integrations page with the Add integration button in the top right"><figcaption><p>Integrations</p></figcaption></figure></div>

6. Search for **PagerDuty**, select it, then click **Next**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FRiMvZQUZPywtgU19IzYG%2Fpagerduty-connect-new-application.png?alt=media" alt="The Connect a new application step with PagerDuty selected"><figcaption><p>Connect a new application</p></figcaption></figure></div>

7. Under **Select Extraction Type**, choose **Direct Configuration** and paste the key you copied into **Access Token**, then click **Next.**

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FvMbXxFi6jK4p5hFaCCxh%2Fpagerduty-direct-configuration.png?alt=media" alt="The Direct Configuration step showing the Access Token field"><figcaption><p>Direct Configuration</p></figcaption></figure></div>

8. Fill **Optional Configuration**, if required.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FZbipc8nl8LTFl5YsVIaj%2Foptional-configuration.png?alt=media" alt="The Optional Configuration step"><figcaption><p>Optional Configuration</p></figcaption></figure></div>

9. Once you have filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status column will read **Connected** and the integration Message will read **Data available**.

{% hint style="info" %}
Teams are only extracted if your PagerDuty account includes the Teams feature. On accounts without it, users and roles are still synced and teams are skipped.
{% endhint %}

### Additional Notes

PagerDuty's API returns a different value for a user's base role than the name shown in the PagerDuty web app. BalkanID displays the name from the web app.

| Shown in PagerDuty  | Returned by the API      |
| ------------------- | ------------------------ |
| Account Owner       | `owner`                  |
| Global Admin        | `admin`                  |
| Manager             | `user`                   |
| Responder           | `limited_user`           |
| Observer            | `observer`               |
| Restricted Access   | `restricted_access`      |
| Full Stakeholder    | `read_only_user`         |
| Limited Stakeholder | `read_only_limited_user` |

PagerDuty does not expose a last-login time for users, so last access is not reported for this integration.


---

# 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.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/pagerduty-integration-setup.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.