We tried to sign up for slack notifications from status.workos.com which is hosted by statuspage, and were turned off by the number of slack permissions it requests
View basic information about public channels in your workspace
View basic information about private channels that Statuspage has been added to
View messages and other content in direct messages that Statuspage has been added to
View the name, email domain, and icon for workspaces Statuspage is connected to
In contrast, adding a slack integration hosted by status.io (such as status.gitlab.com) only asks for scope `incoming-webhook` and has the user pick a channel with no other permissions required.
Hello David,
Thank you for reaching out to StatusPage community. I am Nayan from the StatusPage team, happy to help.
The Slack integration is designed to offer more interactive and flexible notification capabilities. To enable features such as posting updates to multiple channels, sending direct messages, and providing richer context or actions within Slack, Statuspage requests a broader set of permissions.
These permissions allow Statuspage to deliver notifications in a more dynamic way, such as posting to different channels or responding to certain events directly within Slack.
This differs from Status.io’s approach as Status.io’s Slack integration uses only the incoming-webhook
scope. This is a more limited integration that simply allows Status.io to post messages to a specific channel you select, without access to broader workspace or channel information. This approach is more restrictive in terms of functionality but also requires fewer permissions, which can be preferable for organizations with strict security or privacy requirements.
If you have further questions or would like assistance on configuring notifications with minimal permissions, please let us know!
Regards,
Nayan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.