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

# PagerDuty

> Connect PagerDuty so agents can read incidents, services, and on-call, and acknowledge or resolve incidents on request.

Connect PagerDuty so agents can tell you what is firing, who is on call, and
what changed, and acknowledge or resolve an incident when you ask.

> [!NOTE]
>
> PagerDuty is rolling out while Ando's app is in PagerDuty's app review. If
> **PagerDuty** is missing from **Studio → Apps**, it is not available to your
> workspace yet.

## Requirements

* A PagerDuty account with permission to see the incidents, services, and
  schedules agents should use.
* If your PagerDuty account restricts third-party apps, an account admin may
  need to allow Ando's app first.

## Connect

1. Open **Studio → Apps → PagerDuty** and start a connection.
2. Choose **Workspace** for shared team access or **Personal** for your account.
3. Continue to PagerDuty, sign in, and approve access.
4. Back in Ando, give the agent access. For a personal connection, use the
   agent's **Apps** tab.

To check it works, ask the agent which incidents are open and who is on call
for one of your services.

## What agents can do

| Task | Example |
| - | - |
| Read incidents | "What's open on the checkout service right now?" |
| Read on-call | "Who is on call for payments tonight?" |
| Read services and escalation policies | "Who gets paged if the API service goes down?" |
| Search incident history | "How many incidents did search have last week?" |
| Acknowledge or resolve | "Acknowledge the latest incident on checkout." |

Ando asks PagerDuty for these permissions: `incidents.read`,
`incidents.write`, `services.read`, `schedules.read`, `oncalls.read`,
`escalation_policies.read`, and `users.read`. The only write access is to
incidents. Ando cannot change services, schedules, escalation policies, users,
or account settings.

Agents stay within what PagerDuty granted the connected account. Turn off the
incident write tools for any agent that should only read. See
[permission layers](https://docs.ando.so/docs/connecting-apps-to-ando#permission-layers).

## Disconnect

Remove the connection from **Studio → Apps → PagerDuty**. Agents lose access
straight away.

## Troubleshooting

* **Connect fails after you approve access:** reconnect from **Studio → Apps →
  PagerDuty**. If it keeps failing, ask your PagerDuty admin whether Ando's
  app is allowed on your account.
* **A service or incident is missing:** check that the connected PagerDuty
  account can see it, and that the agent is using the right connection.
* **Agent can read but cannot acknowledge or resolve:** check the enabled
  tools, and that the connected account can manage that incident in PagerDuty.

## Support

Ask in **#ando-feedback** inside Ando, or email
[hello@ando.so](mailto:hello@ando.so). See [Ando support](https://ando.so/support).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.