Install app
1
Add Integration
Go to Flashduty On-call Integration Center → Instant Messaging → Slack, click Add.
2
Authorize App
On the redirected Slack page, select Workspace in the top right corner, then click Allow.

3
Save Configuration
Enter data source name, click Save.
Configure war room
After completing the previous steps, in the Flashduty On-call integration configuration page’s Advanced Features section, check Enable War Room to activate this feature—no additional configuration needed.AI SRE controls
Configure the AI SRE switches under Advanced Features; see IM platform for what each one does. Allow AI SRE conversations in IM and AI SRE uses thread replies in regular group chats are on by default, while Allow AI to reply proactively is off by default and needs two extra channel-reading scopes on the Slack app first — see Required permissions. In Slack, Allow AI SRE conversations in IM also controls the/fd command.
Member linking
The Slack integration has no member-linking page: the integration detail page shows only the configuration page, with no Linked Users tab and no One-Click Link button, and Flashduty does not exchange member phone numbers or emails for Slack account IDs to link them in bulk. Slack identifies members by email: when a member acts on an alert card in Slack, Flashduty reads that Slack account’s email and matches it against the member emails of the account, treating a match as that member. So there is nothing to link member by member, but the member’s Slack email and Flashduty member email must match. When they do not, the system replies in Slack with a note that no member matched. Slack is connected per workspace: once the OAuth authorization in Install app completes, channel notifications, @mentioning AI SRE in a group chat, and War Rooms are available in that workspace.Required permissions
When you install the app, Flashduty requests the scopes below through OAuth in one go. They cover basic notifications, War Room, AI SRE conversations, AI-generated post-mortems, and incident notification dispatch, so you normally don’t configure them by hand. If an older integration is missing scopes, click Re-authorize on the integration configuration page.Bot token scopes
The OAuth authorization request does not include
files:read, and the console’s missing permissions check does not test it. For AI SRE to read files and images uploaded in a Slack conversation, add files:read to the Bot Token in your Slack app’s OAuth & Permissions page and reinstall the app; re-authorizing does not add it.
Allow AI to reply proactively depends on the app reading channel messages that do not mention it: public channels through
channels:history, private channels through groups:history. A Slack app authorized before this feature shipped does not have those scopes, so non-mentioned channel messages never reach Flashduty and the assistant has nothing to reply to. The integration detail page then shows the banner “We’ve updated the Slack app. Please reauthorize it.” with a Reauthorize button; clicking it runs the Slack authorization once more, and your existing integration settings and user links are unaffected.User token scopes
The list above matches the current OAuth authorization request. If it differs from what the Slack authorization page shows, the actual request on the authorization page prevails.
Some teams use Slack bot notifications based on Incoming Webhooks instead of this Slack App integration. In that case, enable Incoming Webhooks in that Slack app and include the
incoming-webhook scope in the OAuth flow.FAQ
War Room considerations?
War Room considerations?
- Only one IM integration can have War Room enabled at a time; turn it off in the other integration first. See War Room
- When enabling War Room, the system automatically verifies whether the current Slack app has all required permissions. If missing permissions are detected, a warning message appears on the page with a Re-authorize link
- Click the Re-authorize link to be redirected to the Slack authorization page, which requests the required permissions. After completing authorization, the page automatically returns to Flashduty
- If your Slack integration was authorized before the War Room feature was released, you will typically need to re-authorize on first use to add the new permissions. Re-authorization does not affect your existing integration configuration or user associations
Escalation rule group chat list doesn't have the desired private channel?
Escalation rule group chat list doesn't have the desired private channel?
- Ensure the Install App step completed successfully without errors
- Go to the relevant Slack channel, execute
/invite @Flashdutycommand - When you see
joinedoradded by xxx to xxxprompt, it means successfully added
Escalation rule group chat list doesn't have the desired public channel?
Escalation rule group chat list doesn't have the desired public channel?
- Add the app authorizer to the public channel
- Follow the method from the previous question to add the app to the channel
Why isn't War Room working as expected?
Why isn't War Room working as expected?
- Check again that the app has been granted the required permissions
- If you authorized the Slack IM integration earlier, re-authorize Slack on the Flashduty On-call integration page so the app gets the permissions AI SRE needs
- See the FAQ section in War Room documentation