In order to provide a wide range of functionalities resulting from Calamari integration with Slack, Calamari needs to access certain data from the Slack workspace.

Below you’ll find scopes that access user data and act on behalf of users that authorize them:

  • Slack channels - read and write access.
    Calamari can view basic information about public channels in a workspace in order to provide the functionality of choosing where to post upcoming reminders or receive notifications about clock-in/out.

  • Groups - read and write access.
    Calamari can view basic info about users’ private channels and create new ones on their behalf, for the same reason as access to group channels.

  • User’s identity information (name in Slack workspace, e-mail, teams, domain avatar)
    Calamari reads users’ identities to authorize them during SSO and synchronize profile information.

  • User’s profile data - read and write access
    In order to provide successful status synchronization, Calamari views and edits the user’s profile information accordingly.

Above mentioned data is the only information accessed by Calamari. This results in providing useful and performing integration with Slack, enabling SSO, reminders/notifications, and statuses synchronization. Please note that the admin who’s turning the integration on is prompted with the consent screen where all detailed information is listed.

Did this answer your question?