Slack Permissions
GitNotifier requests Bot Token Scopes only.- We do not request or use Slack User Token Scopes.
Requested Bot Token Scopes
chat:write
Send messages as @GitNotifier.
Why we need it:
- Send direct notifications for GitHub events (new comments, CI failures, PR ready to merge, and similar updates).
commands
Add slash commands and shortcuts.
Why we need it:
- Support Slack command actions like muting/unmuting PRs.
- Support account connect/authorize flows from Slack without requiring App Home navigation.
emoji:read
View custom emoji in a workspace.
Why we need it:
- Support richer message presentation when teams use custom GitHub/PR-related emoji.
im:write
Start direct messages with people.
Why we need it:
- GitNotifier is primarily DM-based to avoid channel spam.
reactions:read
View emoji reactions and associated content where GitNotifier is present.
Why we need it:
- Read user reaction inputs when reactions are used as lightweight actions.
reactions:write
Add and edit emoji reactions.
Why we need it:
- Reflect action status with reactions (for example, adding a success/check reaction).
team:read
View workspace name, email domain, and icon.
Why we need it:
- Show workspace identity (name and icon) in GitNotifier UI for better workspace management UX.
users:read
View people in a workspace.
Why we need it:
- Support GitHub user to Slack user mapping for accurate notifications and mentions. It replaces the Github handle by the Slack handle in the PR notifications (it’s convenient as Github usernames are often different from the Slack usernames).
Scope Philosophy
- Request only scopes required for notification delivery and Slack-side interactions.
- Keep access bot-scoped to reduce permission footprint.