Setup runs in four phases per app: install in Slack, connect to Salesforce, map users, configure features. Coordinate with the Slack workspace admin throughout; Salesforce-side configuration alone does not work without Slack-side install.
- Open Slack Apps Setup
Setup, Quick Find, Slack Apps Setup. The page lists every Slack app that Salesforce supports, with status indicators. Identify which apps need installation versus configuration.
- Install the app in Slack
Coordinate with the Slack workspace admin. The Slack admin installs the app from the Slack App Directory and grants OAuth scopes. Without this, Salesforce-side configuration cannot complete authentication.
- Authenticate in Salesforce
Inside Slack Apps Setup, click the app, click Connect. Authenticate via OAuth using a Slack admin user. The authentication establishes the bi-directional channel between Salesforce and Slack.
- Map users between platforms
Configure user mapping: auto-match by email or manual mapping. Run the mapping job; review unmapped users and resolve manually. Unmapped users get partial functionality; resolve before the rollout date.
- Configure per-app features
Each app has its own feature toggles: channel-creation rules for Sales Elevate, case-driven notifications for Service Cloud, Agentforce channel scope. Configure based on rollout plan and user audience.
Salesforce-for-Slack, Sales Elevate, Service Cloud, Agentforce in Slack, third-party AppExchange Slack apps. Pick based on use case and licensing.
Auto-match by email, manual mapping per user, or bulk CSV import. Auto-match is the default; manual handles edge cases.
Workspace-wide (all channels can use the feature) or per-channel (admins enable specific channels). Trade convenience for control.
Standard permission sets per app (Slack Sales Elevate User, etc.). Assign to the right user audience; avoid broad assignment without role fit.
- Slack-side install and Salesforce-side configuration are separate. Both are required; doing only one leaves the integration half-working.
- User mapping is the most common support-ticket source. Audit unmapped users monthly; new hires often lack mapping until the next sync.
- Slack app versions drift from Salesforce-side support. Watch the Slack Apps Setup version dashboard; re-authenticate when drift surfaces.
- Permission sets gate access. Without the right permission set, users cannot use the integration even if installation and mapping are correct.
- Enterprise Grid Slack deployments add cross-workspace complexity. Document which Salesforce org connects to which workspace before configuration.