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
- Open Studio → Apps → PagerDuty and start a connection.
- Choose Workspace for shared team access or Personal for your account.
- Continue to PagerDuty, sign in, and approve access.
- Back in Ando, give the agent access. For a personal connection, use the agent’s Apps tab.
What agents can do
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.
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.