My team won't allow Akiflow to connect with slack due to the scopes requested. Specifically, requiring access to all channels including private ones. Could we limit the scopes requested or create different versions of scopes?
Currently, it's not possible to achieve what you're suggesting. Please note that the type of access we are requesting only allows us to view basic information and not the content (i.e. the messages) of the channels. The scopes channels:read, groups:read, im:read, and mpim:read grant Akiflow access to what Slack refers to as "basic information." You can find more details in the Slack documentation here: https://api.slack.com/scopes
To access the messages within the conversations, we would need to request the following scopes: channels:history, groups:history, im:history, and mpim:history. However, Akiflow is not requesting these scopes at this time.
I understand that, depending on the nature of your business, the names of private channels could pose a privacy concern.
Log in to comment and vote
Comments1
Sebastian
Oct 17, 2023
Hello Cyan,
Currently, it's not possible to achieve what you're suggesting. Please note that the type of access we are requesting only allows us to view basic information and not the content (i.e. the messages) of the channels. The scopes
channels:read,groups:read,im:read, andmpim:readgrant Akiflow access to what Slack refers to as "basic information." You can find more details in the Slack documentation here: https://api.slack.com/scopesTo access the messages within the conversations, we would need to request the following scopes:
channels:history,groups:history,im:history, andmpim:history. However, Akiflow is not requesting these scopes at this time.I understand that, depending on the nature of your business, the names of private channels could pose a privacy concern.