Security Overview: Security policies and reports
Our AI slack bot has many features. However, for the sake of brevity, this doc will focus on the specific permissions and security details that the integration requires. For a general overview of what Cal is, and what interactions we offer, you should visit this page: ‣
Support agents can directly message Cal. Cal will be able to read all messages in that direct message thread, and we will store the messages in our internal database for review and model evaluation.
You can add Cal as a bot into any slack channel. Cal will be able to read all messages in the channel they are in, but we will only store messages that Cal was explicitly a part of.
Here’s a list of our current offerings for what Cal can do in a slack channel:
In a slack channel, Cal will only reply to messages that they are tagged in. Cal will not be reading any other message that it’s not tagged in. Cal will have write access to the thread its tagged in to write a response.
If enabled, Cal will be able to read past chats in the slack channel, audit those questions against its knowledge base, and send an alert to the channel if it detected missing knowledge. Cal does NOT store any data when it sends this missing alert, however if the admin chooses to save the knowledge, it will be stored in a shared Google Drive folder.
Our slack bot has the following auth scopes:
chat:write - These are used to reply in threadschat:write.customizechat:write.public