OAuth Permission Scopes

Last edited: Sep 18, 20

Reasoning behind the OAuth Perimission Scopes We Use

Permission (OAuth) scopes are the permissions that OpenSay requires to function properly in Slack. You might find it useful to view Slack's guidance about understanding these permissions scopes.

Please note that OpenSay is unable to add new permission scopes unless users reinstall the app on Slack.


Add the /anon command and the Post Anonymously, Poll Anonymously and Open Menu shortcuts.


Post anonymous messages, polls, replies and help messages.


Automatically join public channels where you use OpenSay, without you needing to manually /invite @OpenSay.


Respond to direct mentions of the OpenSay app, to display help text about how to use the app.


Keep OpenSay up to date when a workspace domain or name changes, which helps prevent some bugs. Also used to display the workspace icon in the OpenSay dashboard.


We offer OpenSay for free for educational / open source / non-commercials teams that are on Slack's free plan. To know whether a team is on a paid / free plan we need access to this scope.

channels:read, groups:read, usergroups:read

Keep an up-to-date state of name and ids of channel, groups (invited only) and usergroups for our channel whitelisting feature (and soon usergroup whitlisting feature). OpenSay can't read messages in those channels.


Deliver notifications to individual users. For instance, in the case of a problem with the creation of an anonymous message or poll.


View messages and mentions of OpenSay in user's direct message channel with OpenSay.

users:read, users:read.email

Count the number of users in a workspace (for our pricing model) and save a per user state (e.g. indication if an onboarding message has already been sent). We use email addresses to respond to feedback, to contact admins regarding the product and billing.


On topic product info and updates

No spam. Unsubscribe anytime.

ISO27001 Compliance
In Progress
GDPR Compliance

Heterodox Ltd.© 2024