Slack permissions

To maintain a seamless communication experience for developers we synchronize conversations between Slack and GitHub. To do so, we require some permissions from your organization's Slack workspace. Understand why and how we use these OAuth scopes below:

Application scopes

Bot scopes

Bot scopes	Reason
bookmarks:read	Read bookmarks in PR channels created by Pullpo in order to update them with relevant information.
bookmarks:write	Update bookmarks in PR channels with relevant information.
channels:history	View messages in public PR channels that @Pullpo has created to synchronize the conversation with GitHub.
channels:manage	Create a public PR channel when a new pull request is opened and archive them when it's merged or closed.
channels:read	Check the state of public PR channels: what members it has and if it is archived (e.g. when a pull request is reopened).
chat:write	Send messages through PR channels as @Pullpo with relevant information (alerts for: new commits, approved reviews, etc.).
chat:write.public	Send relevant alerts through public channels as @Pullpo.
groups:history	View messages in private PR channels taht @Pullpo has created to synchronize the conversation with GitHub.
groups:read	Check the state of private PR channels: what members it has and if it is archived (e.g. when a pull request is reopened).
groups:write	Create a private PR channel when a new pull request is opened and archive them when it's merged or closed.
im:read	Receive direct messages sent to @Pullpo.
im:write	Send individual insight requests to members when there is a significant deviation from a squad's metrics.
team:read	Obtain information about the organization that installs Pullpo to personalize some aspects of the application.
users:read	View people in the workspace to be able to link their identifiers to the corresponding GitHub identifiers.

Events

Subscriptions	Reason
message.channels	Send the new message in a public PR channel to the corresponding GitHub PR discussion page.
message.groups	Send the new message in a private PR channel to the corresponding GitHub PR discussion page.