This legacy integration enables you to draft and schedule multiple employee communications for Slack through the Employee Email web app.

In This Article

• Prerequisites
• How to sync Employee Email with your organization's Slack workspace
• Known limitations of Slack via Employee Email
• Required Scopes for Employee Email's Slack bot

Prerequisites

• An existing Slack workspace
• A Slack account to maintain the sync
  Staffbase recommends using a service account rather than an individual user’s account
• An Employee Email Admin or Parent Admin account

Setting Up Slack via Employee Email (Legacy)

To enable sending and scheduling messages in Slack via Employee Email, start by syncing your Slack workspace.
Any messages sent via Employee Email will display the legacy Bananatag Display Image and Display Text by default. These can be customized for your organization.

1. In a new Incognito or InPrivate browser window, sign into the Employee Email web app.
2. Click your avatar to open the profile menu.
3. Click Settings.
4. Click the Chat Apps tile.
   Optionally, upload a customized Display Image for the Bananatag App bot that will appear in your Slack workspace, and edit its Display Text.
5. Click Sync Account.
6. Enter the name of your organization's Slack workspace and click Continue.
7. Sign in with the Slack account that will be used to maintain the sync.
   Staffbase recommends using a service account rather than an individual user’s account.
8. Click Allow to sync with your workspace.
   You are taken back to Chat Apps, where Slack displays as Synced.

Known Limitations

• Only one Slack workspace can be synced for each Employee Email license.
• Slack can only be set up by an Admin or Parent Admin. It will then be available for all Employee Email users who have permission to Send/Schedule chat messages.
• Employee Email can only post to public channels. This means you are unable to send to private groups, channels, DMs, or group DMs.
• Due to limitations of the Slack scheduling API, messages cannot be scheduled more than 120 days ahead of time.
• Once a Slack message has been sent, it cannot be deleted. However, you can delete messages before sending them.
• Employee Email uses a bot to send messages in Slack.
  Any messages sent via Employee Email will display the legacy Bananatag logo and Display Text by default. These name can be customized for your organization.
  Here's how it looks without any customization:
  
• When a message is scheduled, our bot will be automatically added to the channel. This will create a notification as seen below:
  
  

Your IT team may also request to see Employee Email's required Slack bot scopes. Below are all of the permissions that our bot requires.

Required Bot Scopes

• channels:read - View basic info of public channels in the workspace
  This is used for listing available channels to send to
• chat:write - Send messages as Bananatag (Display Text can be customized)
• chat:write:public - Post to any public channel without joining
• reactions:read - View emoji reactions and their associated content in the channels and conversations that the bot has been added to
• team:read - View name, email domain, and icon for workspaces that the bot is connected to
• channels:join - Join a channel so that the bot is able to schedule messages to that channel. 

User scopes

• users.profile:read - View details of people in the workspace.
  
  Note: This is not being used to read details, but because Employee Email needs at least one user scope to get a user token, which enables you to uninstall our bot.

What we won’t have access to

• Reading or writing to private groups, private channels, DMs, group DMs
• Sending on behalf of a user
  
  Note: All interactions will be done on behalf of Bananatag (Display Text can be customized).
  It will not be possible to post as a user via this integration.