Slack permissions
When you connect Slack to StatusGator, we request certain permissions in order to deliver service status updates directly to your team. Below is a breakdown of each permission we request, what it allows us to do, and why it’s necessary. Notably, we do not have permission to read any messages from your Slack workspace.
| Permission | What It Allows | Why We Need It |
|---|---|---|
chat:write | Allows the app to send messages to channels | StatusGator uses this permission to post status updates into your selected Slack channels. |
chat:write.public | Allows the app to send messages to channels it hasn't been invited to | Enables StatusGator to post updates even if the app hasn’t been manually invited to every channel. |
chat:write.customize | Allows the app to send messages with customized usernames and avatars | Lets StatusGator messages appear with a custom name and icon, making updates more recognizable in your Slack workspace. |
commands | Enables the use of Slash commands | This allows you to interact with StatusGator via Slack Slash commands (e.g., /statusgator) for quick access to service statuses or settings. |
team:read | Provides basic team information including the workspace name | Used to display relevant information on the Slack app integration page and to personalize your StatusGator integration. |
channels:read | Access to public channel metadata | Allows StatusGator to list your available public channels when setting up notifications. |
groups:read | Access to private channel metadata | Lets StatusGator display private channels in your integration setup, so you can send alerts to them if desired. |
links:read | Lets the app receive metadata about shared URLs | Required if you want StatusGator to unfurl status links shared in Slack messages (i.e., show a preview when a link is posted). |
links:write | Allows the app to show rich previews of links | Used in combination with links:read to display rich previews of status links shared in Slack. |