Conversation
Add new bot scopes (app_mentions:read, channels:history, groups:history, reactions:read, reactions:write) and bot event (app_mention, reaction_added) required for Seer Explorer and other new features. Add users:read.email to user scopes. Reformat MDX to use standard bold syntax and fix whitespace. Refs ISWF-2351 Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
leeandher
commented
Apr 7, 2026
Member
Author
There was a problem hiding this comment.
Quite a bit of this was done by my auto-formatter, only added to the scope table and list of event subscriptions
alexsohn1126
approved these changes
Apr 15, 2026
Member
alexsohn1126
left a comment
alexsohn1126
left a comment
There was a problem hiding this comment.
Just one small change, otherwise looks good!
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Comment on lines
+78
to
+88
| | `chat:write.public` | Post notifications to public channels the bot hasn't been invited to. | | ||
| | `commands` | Power the `/sentry` slash command: `link`/`unlink` (identity), `link team`/`unlink team` (channel-to-team mapping), and `help`. | | ||
| | `groups:read` | Same as `channels:read` but for private channels. | | ||
| | `groups:history` | (Optional) Same as `channels:history` but for private channels. | | ||
| | `im:history` | Receive `message.im` events for the bot's help responses in DMs, and fetch DM thread history for Seer Explorer context. | | ||
| | `im:read` | Receive direct-message events and resolve DM channel metadata, enabling slash commands and messages sent directly to the bot. | | ||
| | `links:read` | Receive `link_shared` events when a user pastes a Sentry URL in Slack so the integration can generate a rich preview. | | ||
| | `links:write` | Attach rich unfurl previews (issues, Discover queries, metric alerts) to Sentry URLs shared in Slack. | | ||
| | `team:read` | Fetch the workspace name and icon during installation for display in the Sentry integration settings page. | | ||
| | `users:read` | Look up workspace users to validate alert-rule recipients, search by username/display name, and automatically link Sentry accounts to Slack identities by email after installation. | | ||
|
|
There was a problem hiding this comment.
Bug: The documentation is missing the reactions:read and reactions:write bot scopes and the reaction_added bot event, which were intended to be added in this pull request.
Severity: MEDIUM
Suggested Fix
Update the Bot Token Scopes table in develop-docs/integrations/slack/index.mdx to include reactions:read and reactions:write. Also, add reaction_added to the list of subscribed bot events to match the functionality described in the commit message.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: develop-docs/integrations/slack/index.mdx#L71-L88
Potential issue: The commit message `320eb5b1` indicates that new Slack bot scopes
(`reactions:read`, `reactions:write`) and a bot event (`reaction_added`) were to be
added to the documentation. However, these items are missing from the final version of
the `index.mdx` file. While other scopes from the same commit were successfully added,
the omission of these three suggests they were accidentally dropped, possibly during a
subsequent 'correct docs' commit. If the Sentry Slack integration requires these
permissions for features like Seer Explorer's reaction handling, users following the
documentation will have a misconfigured application, leading to broken functionality.
Did we get this right? 👍 / 👎 to inform future reviews.
leeandher
deleted the
leanderrodrigues/iswf-2351-prepare-docs-for-users-the-new-scopes-we-require
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
updates docs for the new scopes!