@@ -63,6 +63,11 @@ On the same page under **Scopes** you'll need to add **Bot Scopes** and **User S
6363
6464Add the following scopes to **Bot Scopes** :
6565
66+ <Alert title="Note (for self-hosted users)">
67+ ` channels:history` , `groups:history`, and `app_mentions:read` are used to trigger Seer which is
68+ not currently available for self-hosted, meaning they're not required permissions to add.
69+ </Alert>
70+
6671| Scope | Reason |
6772| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
6873| `app_mentions:read` | Receive `app_mention` events when the bot is mentioned (e.g. @Sentry) in a message. |
@@ -76,8 +81,6 @@ Add the following scopes to **Bot Scopes**:
7681| `groups:history` | (Optional) Same as `channels:history` but for private channels. |
7782| `im:history` | Receive `message.im` events for the bot's help responses in DMs, and fetch DM thread history for Seer Explorer context. |
7883| `im:read` | Receive direct-message events and resolve DM channel metadata, enabling slash commands and messages sent directly to the bot. |
79- | `reactions:read` | Look up the reactions associated with a message. |
80- | `reactions:write` | Add/remove reactions from the bot to messages in the workspace. |
8184| `links:read` | Receive `link_shared` events when a user pastes a Sentry URL in Slack so the integration can generate a rich preview. |
8285| `links:write` | Attach rich unfurl previews (issues, Discover queries, metric alerts) to Sentry URLs shared in Slack. |
8386| `team:read` | Fetch the workspace name and icon during installation for display in the Sentry integration settings page. |
@@ -115,10 +118,9 @@ You’ll see “Verified” when you’ve entered the correct URL.
115118
116119Still on the **Event Subscription** page, go to **Subscribe to bot events** and add the following bot user events :
117120
118- - ` app_mention`
121+ - ` app_mention` (Not supported for self-hosted)
119122- ` link_shared`
120123- ` message.im`
121- - ` reaction_added`
122124
123125and next go to **Subscribe to events on behalf of users** and add the following event :
124126
@@ -141,10 +143,10 @@ Navigate to **Slash Commands** under **Features**. Click **Create New Command**
141143| Command | `/{yourname}-sentry` |
142144| Request URL | `{YOUR_DOMAIN}/extensions/slack/commands/` |
143145
144- <Alert title="Note">
145- If you're a Sentry employee, when creating the slash command avoid using `/sentry`, try something
146- like `/{your_name}-sentry`. If multiple apps are installed with the same slash command, the most
147- recently installed one takes over .
146+ <Alert title="Note (for Sentry employees) ">
147+ When creating the slash command avoid using `/sentry`, try something like `/{your_name}-sentry`,
148+ if using a shared test workspace. When multiple apps are installed with the same slash command,
149+ the most recently installed one takes precedence .
148150</Alert>
149151
150152At the bottom of the page, click **Save**.
0 commit comments