The guide is sequential. Allocate two to four hours of focused admin time and coordinate with the Slack admin in advance; some steps require Slack-side actions that cannot be performed from Salesforce alone.
- Open Guided Slack Setup
Setup, Quick Find, Guided Slack Setup. The guide opens at step 1. Read the prerequisite list; confirm the Salesforce edition supports Slack integration and a Slack admin is available for the handoff steps.
- Coordinate the Slack-side install
Send the auto-generated Slack-admin task list (deep links plus written steps) to the Slack admin. They install the apps and grant OAuth scopes. Verify completion in the guide''s validation step before proceeding.
- Authenticate the connection
Click Connect inside Guided Slack Setup. Authenticate via OAuth using a Slack admin user. The guide stores the tokens and validates bi-directional connectivity.
- Run user mapping
The guide runs auto-match by email. Review unmapped users; resolve manually or bulk-import via CSV. Most orgs hit 90% auto-match. The guide flags remaining gaps as warnings, not blockers.
- Configure features and run health check
Enable Slack Channels for Records per object as needed. Configure any Sales Elevate or Service Cloud features. Run the integration health check; resolve any failures before declaring the deployment done.
Strictly sequential; later steps unlock only when earlier ones pass validation. Skipping is not supported.
Auto-match by email, manual mapping for edge cases, bulk CSV import. Most orgs use a combination across the rollout.
Enable per-object Slack Channels for Records, Sales Elevate features, Service Cloud features, Agentforce in Slack per the deployment plan.
Per-step rollback. Reverse only the steps that need fixing; the rest of the integration stays intact.
- Several steps require Slack-side actions. Coordinate with the Slack admin team in advance; without their availability the guide stalls.
- Auto-match-by-email user mapping fails when Salesforce and Slack accounts use different email domains. Bulk CSV import handles these edge cases.
- Feature configuration in the guide is a starting set. Full per-object channel-for-records rules need detailed configuration in Slack Apps Setup after the guide completes.
- The guide is for initial rollout, not ongoing operations. Day-to-day changes happen in Slack Apps Setup; revisiting the guide for routine changes is overhead.
- Permission sets are not configured by the guide. Assign permission sets to users separately after the guide completes; otherwise users cannot use the features the guide enabled.