Setting up CultureAI's Slack integration using our wizard is quick and easy, but different permissions are required based on functionality needs.
CultureAI's Slack integration offers key capabilities supporting the following use cases:
1. Instant Messaging Use:
2. MFA Use
3. Mobile Device Use
Not keeping mobile device updated
4. Workstation Security
Not keeping desktop updated
CultureAI requires different permissions (levels of admin access within Slack) in order to provide the capabilities above. Required Permissions are as follows:
'chat:write', 'app_mentions:read' - Detecting and replying to mentions in the chat
'chat:write.public' - Write to public channels without being added to them first
'users:read' - Access to users.list
'channels:read', 'groups:read', 'im:read', 'mpim:read' - For conversations.info channel listing
'im:write', 'conversations.open' - For when we direct message
Other Permissions:
Phishing requires basic permissions, plus the following:
'users:read.email', 'users.profile:read' - To read user profiles for names/icons & mapping users to employees
'channels:history', 'groups:history', 'im:history', 'mpim:history' – Read message history in all channels, groups, etc
'chat:write.customize' - To send with a different name/icon
MFA Status requires basic permissions, plus the following:
'users:read.email', 'users.profile:read' - To read the has_2fa flag on users and map them to employees
Access Logs requires basic permissions, plus the following:
'users:read.email' - To map Slack users to employees
'admin' - To use team.accessLogs
Message Scanning requires basic permissions, plus the following:
'users:read.email' - To map Slack users to employees
'channels:history', 'groups:history', 'im:history', 'mpim:history' - To receive message events
'chat:write' - To delete the message
Message Reporting requires basic permissions, plus the following:
'commands', 'users:read.email' – Provide our right-click context menu for message reporting