For more detailed information on all scopes requested by the PagerDuty Slack application, see the full listing here.

2025-03-10

Added the following bot token scopes: assistant:write, im:history.

The im:history permission gives PagerDuty the ability to read direct messages sent to the PagerDuty app. This can be used to ask the PagerDuty app for help directly, or to interact with PagerDuty within a group direct message.

If PagerDuty Advance is enabled for your organization, assistant:write allows you to interact with Advance using a new messaging interface, interacting with PagerDuty alongside your work in channels and direct messages (DMs).

2025-02-03

Change

Added the following optional bot token scopes: channels:history, groups:history, reactions:read, reactions:write.

For workspaces connected prior to February 3, 2025, we will not request these scopes unless you explicitly opt-in, by enabling the associated settings on the Slack configuration screen in the PagerDuty web application.

For any newly added workspaces, we will request these scopes, however you may immediately opt-out by disabling the associated settings on the Slack configuration screen in the PagerDuty web application.

Purpose

The PagerDuty Slack application now allows customers to leverage PagerDuty Advance directly from the PagerDuty Slack app, without needing to install the separate PagerDuty Advance Slack app. If you are already using the PagerDuty Advance Slack app, you may enable these optional scopes and uninstall the PagerDuty Advance app.

Additionally, the PagerDuty Slack application now supports ingesting Slack data into Jeli for post-incident analysis. With these new scopes enabled, PagerDuty can automatically ingest the contents of your dedicated Slack channel into your Jeli Opportunity.

2024-11-22

Change

Added the following bot token scope: bookmarks:write.

Purpose

This scope is used to enable the Add a Bookmark incident workflow action.