AI SRE Required Permissions
The following list includes all permissions required when the Slack IM integration uses AI SRE, including basic notifications, War Room, AI SRE conversations, and AI-generated post-mortem reports. If you use the official Flashduty Slack app, complete authorization or re-authorization from the Flashduty page. If you use a self-managed Slack app, confirm each Bot Token Scope in Slack OAuth & Permissions.| Official permission name | Purpose |
|---|---|
chat:write | Send alert notifications, War Room messages, AI SRE replies, and streaming message updates |
app_mentions:read | Receive AI SRE messages that mention @Flashduty in channels |
im:history | Receive and read direct messages with the Flashduty Bot |
channels:history | Read public channel history for AI SRE context and AI-generated post-mortem reports |
groups:history | Read private channel history; required when War Rooms are created as private channels |
channels:manage | Create and manage public channels |
groups:write | Create and manage private channels |
groups:write.invites | Invite members to private War Room channels |
channels:read | Read public channel metadata |
groups:read | Read private channel metadata and War Room details |
users:read | Read basic Slack user information |
users:read.email | Match and automatically link Slack users by email |
reactions:write | Add or remove confirmation reactions while AI SRE processes messages |
files:read | Download images or files sent to AI SRE in conversations |
1. Install App
Authorize App
On the redirected Slack page, select Workspace in the top right corner, then click Allow.
2. Configure War Room
After completing the previous steps, in the Flashduty On-call integration configuration page’s Enhanced Features section, check Enable War Room to activate this feature—no additional configuration needed.If your Slack integration was authorized before War Room or AI SRE was released, first confirm that the AI SRE required permissions have been added through re-authorization.
3. Linked Users
In the Linked Users tab of the integration detail page, you can view the linking status between team members and Slack accounts, and quickly complete batch linking.View Linking Status
The linked users list shows all team members and their linking status. You can filter by:| Filter | Description |
|---|---|
| All | View all team members |
| Linked | View only members who have linked their Slack accounts |
| Unlinked | View only members who have not yet linked their Slack accounts |
One-Click Linking
When unlinked members exist, click the One-Click Link button. The system will attempt to obtain Slack account IDs via phone numbers or emails and automatically link them, equivalent to members logging into Flashduty using the same information on Slack.4. FAQ
War Room considerations?
War Room considerations?
- Only one IM integration can have War Room enabled at a time. If you have already enabled War Room in another IM integration (such as Dingtalk, Feishu/Lark, or WeCom), you need to disable it there first before enabling it in the current Slack integration
- 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 AI SRE required permissions listed at the beginning of this page (including channel management, message read/write, user info reading, etc.). 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
Error when clicking 'Allow' button during authorization?
Error when clicking 'Allow' button during authorization?
Error when clicking 'Save' button?
Error when clicking 'Save' button?
Slack App shows not_authed error?
Slack App shows not_authed error?
Please try again, this may be a temporary Slack service issue. If the error persists after retry, please contact customer service.
Slack App shows Operation timed out error?
Slack App shows Operation timed out error?
Please try again. This may be server-Slack communication timeout. If the error persists after retry, please contact customer service.
Slack App shows Status Code 500 error?
Slack App shows Status Code 500 error?
Please try again. This may be a Flashduty On-call server error (e.g., data source was disabled). If the error persists after retry, please contact customer service.
Slack App shows other unknown errors?
Slack App shows other unknown errors?
Please try again. If the error persists after retry, please contact customer service to log and resolve new issues.
Why isn't War Room working as expected?
Why isn't War Room working as expected?
- For previously authorized Slack IM integrations, manually re-authorize Slack in the Flashduty On-call integration configuration page so the app obtains the AI SRE required permissions listed at the beginning of this page
- See the FAQ section in War Room documentation