> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-setup/notifications/platform-setup/pagerduty-setup-for-organization-notifications.md).
# PagerDuty Setup for Organization Notifications
This guide is the first step of a larger process to enable organization notifications.
{% hint style="info" %}
After completing the steps on this page, you will be instructed to go to [Manage Organization Notifications](/workbench-setup/notifications/manage-organization-notifications.md) to set up your actual notifications.
{% endhint %}
## Step 1: Set Up the Integration in Workbench
Notifications can only be sent to a single PagerDuty service.
{% hint style="warning" %}
After a security incident is resolved in Workbench, you must manually resolve the incident in PageDuty.
{% endhint %}
1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. Select **Organization Settings > My Organization**.
* If you have multiple organizations, you must also select the appropriate organization name from the list.
3. Scroll down and select the **Integrations** tab.
4. Under PagerDuty, select **Add a Pagerduty destination** and then select **Open PagerDuty** to begin integration.
5. A new tab opens in your browser; log in with your PagerDuty credentials.
6. In PagerDuty, select which service you want to add the integration to or create a new integration, then select **Connect**.
{% hint style="warning" %}
You can only select one service.
{% endhint %}
7. Back in Workbench, look for an **Enabled** banner in the PagerDuty section.
8. Now, select the **Test connection** link to test the connection. The test creates and closes an incident in PagerDuty.
9. Back in PagerDuty, navigate to your **Incidents** page.
10. In the **Activity for the Past 7 Days** section, look for the test connection. It will have a unique ID appended to the title, and two rows for the test event (one for the triggered event and one for the resolved activity).
## Step 2: Add Your Organization Notifications
Now you can begin setting up your organization notifications. See [Manage Organization Notifications](/workbench-setup/notifications/manage-organization-notifications.md) for instructions.
{% hint style="info" %}
For a list of default notifications, see [Default Organization Notifications](/workbench-setup/notifications/about-notifications.md#default-organization-notifications). You can edit these notifications at any time using the instructions in the linked guide above.
{% endhint %}
---
# 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.expel.io/workbench-setup/notifications/platform-setup/pagerduty-setup-for-organization-notifications.md?ask=&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.
