Manage Slack Connection
Manage Slack Connection is a Setup page in Salesforce that configures and maintains the connection between a Salesforce org and one or more Slack workspaces.
Definition
Manage Slack Connection is a Setup page in Salesforce that configures and maintains the connection between a Salesforce org and one or more Slack workspaces. The page provides controls for authenticating the connection through OAuth, mapping Salesforce records to Slack channels, configuring which users can use Slack-aware features, and monitoring the health of the integration over time. It is the central operational surface for any Salesforce-to-Slack integration that the org has enabled.
Salesforce acquired Slack in 2021 and has since built deep integration between the two platforms. The Manage Slack Connection page is the front door to that integration, used by admins to wire up features like Slack record sharing, Salesforce sales notifications in Slack channels, Slack-based approval routing, and the Service Cloud-Slack agent collaboration features. Each enabled feature reads from the connection configuration on this page.
Manage Slack Connection: what it controls and how to operate it
What the Manage Slack Connection page actually controls
The Manage Slack Connection page in Setup holds four configuration areas. First, the OAuth credentials that link the Salesforce org to a Slack workspace, including the workspace name, the connected Slack app, and the authorization scopes granted. Second, the channel mapping settings that let admins pair Salesforce objects (Accounts, Opportunities, Cases) with Slack channels for record sharing and notifications. Third, the user mapping that maps Salesforce users to their corresponding Slack identities, either through email matching or through SSO. Fourth, the feature-level toggles that enable or disable each Salesforce-Slack feature individually. Changing settings on this page affects every user in the org who uses the integration, so changes go through standard org change management.
OAuth setup and the connected Slack app
Setting up the connection starts with installing the Salesforce-provided Slack app into the target Slack workspace. The Slack admin grants the app the required OAuth scopes (channels:read, chat:write, users:read, files:read, and others depending on features). The Salesforce side stores the resulting OAuth token in the Connected App configuration that backs the Manage Slack Connection page. Tokens do not auto-rotate; if the Slack workspace admin revokes the app or rotates the secret, the Salesforce side has to re-authorize. The platform sends an alert email to the Salesforce admin when the connection fails or the token is about to expire. Monitor the email or build a dashboard alert that surfaces connection-health failures, since broken connections silently disable every downstream Slack feature.
Channel mapping for record sharing and notifications
Channel mapping is where Salesforce records get associated with Slack channels. The pattern lets a deal team share an Opportunity record into a Slack channel as a Slack object, where channel members can see live record updates without leaving Slack. The mapping is configured per object: which fields appear in the Slack object, which user permissions are needed to share, which channel types (public, private, direct message) are allowed. Service Cloud has a similar pattern for Cases, where Cases can be shared into Slack channels for swarm-based support. The channel mapping configuration controls all of this from a single place, with per-object enable toggles and per-feature audit logging.
User identity mapping and SSO integration
For a Salesforce user to interact with the Slack integration, the platform needs to know which Slack user identity corresponds to which Salesforce user identity. The Manage Slack Connection page supports two mapping modes. Email matching uses the user email address as the cross-platform key; works for orgs where Salesforce and Slack emails match. SSO mapping uses the SAML or OIDC identity provider that authenticates both Salesforce and Slack; works for orgs where central identity governs both. SSO is the recommended mode because it survives email changes (someone gets married, changes their email) and provides cleaner audit. Configure the mapping mode once at integration setup; switching modes later requires re-mapping every user.
Feature toggles and granular enablement
Salesforce-Slack integration is not one feature; it is a portfolio. The Manage Slack Connection page lists each feature as a separate toggle: Sales Notifications, Account Plans in Slack, Service Cloud for Slack, Slack Sales Elevate, Approval Routing through Slack, and so on. Each feature has its own enablement state, its own user permissions, and its own configuration page accessible from the parent Manage Slack Connection page. Mature orgs roll out features one at a time, with a pilot user group and a feedback period before enabling each feature org-wide. The feature-level toggles let the admin disable a problematic feature without breaking the rest of the integration.
Connection health monitoring and troubleshooting
The Manage Slack Connection page shows a connection-health status: OK, Warning (token expiring soon), or Error (token revoked, app uninstalled, scopes changed). The page also shows the last successful sync time for each feature, the most recent error message if any, and a Test Connection button that issues a smoke-test call to Slack. Common failure modes include the Slack admin uninstalling the Salesforce app from the workspace, the user identity mapping breaking after an email change, the OAuth token expiring after a long period of inactivity, and Slack scope changes requiring re-authorization. The first place to look when any Salesforce-Slack feature breaks is the connection health on this page, before chasing per-feature bugs.
Setting up and operating the Salesforce-Slack connection
Setting up Manage Slack Connection is a coordinated activity between the Salesforce admin and the Slack workspace admin. The four-step process covers: install the Salesforce app into Slack with the right OAuth scopes, authorize the connection from the Salesforce side, configure user identity mapping, and enable the specific Salesforce-Slack features the org wants. After that, ongoing operation is monitoring the connection health and re-authorizing when tokens expire. Each step is short on its own, but skipping any of them leaves a half-working integration that confuses users.
- Install the Salesforce app into the Slack workspace
Have the Slack workspace admin install the Salesforce app from the Slack App Directory. The install prompts for OAuth scope approval; grant the scopes the Salesforce documentation lists (channels:read, chat:write, users:read, files:read, and others). After install, the Slack admin sees the Salesforce app in the workspace app list. Configure the app allowed channels and user audience per Slack workspace policy. Capture the workspace name and the Slack app Client ID; the Salesforce side needs both to authorize the connection.
- Authorize the connection from Manage Slack Connection
In Salesforce, open Setup, search Manage Slack Connection. Click Connect to Slack. Enter the Slack workspace name and follow the OAuth flow to authorize the connection. The Salesforce platform stores the resulting refresh token in the Connected App configuration. After the OAuth flow completes, the Manage Slack Connection page shows the workspace as Connected with a green status indicator. Test the connection with the Test Connection button; a successful test sends a smoke-test message to a test channel. Document the connection details (workspace name, connection date, granted scopes) in the integration runbook.
- Configure user identity mapping
On the Manage Slack Connection page, navigate to User Mapping. Choose between Email Matching and SSO Mapping. For Email Matching, confirm that the Salesforce User Email field matches the Slack User Email; users with mismatched emails cannot use the integration until the mapping is fixed. For SSO Mapping, confirm both Salesforce and Slack are connected to the same SAML or OIDC identity provider. Run a User Mapping Audit Report to identify any users whose Slack identity cannot be determined; resolve each before declaring the integration ready for general use.
- Enable features and roll out to user groups
On the Manage Slack Connection page, enable the specific features the org wants (Sales Notifications, Account Plans, Service Cloud for Slack, etc.). Each feature has its own configuration sub-page; complete the configuration for each enabled feature. Roll out features in waves: a pilot user group for two weeks, expand to 25 percent of users for one week, then 50 percent, then full population. Capture user feedback at each wave and adjust the configuration as needed. Document the rollout schedule and the feature-by-feature ownership in the integration runbook so future admins inherit a clear picture.
- OAuth tokens do not auto-rotate. If the Slack workspace admin revokes the app or rotates the secret, every Salesforce-Slack feature fails until re-authorization. Monitor the connection health email alerts.
- Email Matching mapping breaks the moment a user email changes (marriage, name change, departmental email rebrand). SSO Mapping is more resilient; pick it during initial setup if SSO is available.
- Disabling the Salesforce app in Slack does not auto-update the Manage Slack Connection status to Error immediately. The first user impact may surface before the dashboard does; build proactive monitoring.
- Feature toggles are org-wide. Enabling Sales Notifications affects every user in the org, not just the pilot group. Use per-feature permission sets or profile permissions to limit the audience before enabling.
- Slack scope changes (new feature requires a new scope) require re-authorization, not just an update. Plan for re-auth during quarterly Salesforce releases when new Slack features ship.
Trust & references
Straight from the source - Salesforce's reference material on Manage Slack Connection.
- Manage Slack ConnectionSalesforce Help
- Set Up the Salesforce-Slack IntegrationSalesforce Help
- Slack OAuth 2.0 DocumentationSlack API Docs
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Manage Slack Connection represent in the Salesforce Platform?
Q2. Who can benefit from understanding Manage Slack Connection?
Q3. What architecture concept is Manage Slack Connection an example of?
Discussion
Loading discussion…