Slack's June 2026 admin update is one of the most CRM-relevant releases in months. It adds private Salesforce channels, Slackbot actions that create and edit Salesforce records, self-serve email and activity logging for Slack CRM users, and a set of new Slackbot AI capabilities — plus two deprecation items that require admin action on a deadline.
This guide summarizes every item in the June 2026 update, explains what each one means for admins and Salesforce teams, and flags the two changes with hard dates: the Windows .exe installer deprecation (March 2027) and the FedRAMP support-data change (request deadline August 19, 2026).
What it is: Slack's June 2026 admin update introduces 12 new features (including private Salesforce channels, Slackbot Salesforce actions, Slackbot web search, and Focus mode), previews 5 upcoming capabilities, and announces 2 deprecations that require action. Who it matters for: Slack workspace admins, org owners, IT teams that deploy Slack on Windows, and revenue teams using Slack as a front end for Salesforce. What to do: review the new AI defaults (Slackbot web search is off by default), plan the move from the legacy .exe installer to MSIX before March 2027, and — for FedRAMP customers — have your Primary Owner submit a support-data request before August 19, 2026 if support data must stay in the FedRAMP boundary. Why Vantage Point: Vantage Point helps teams operationalize Slack and Salesforce together — channel strategy, record automation, governance, and adoption — so these features turn into measurable CRM workflow improvements.
The update covers three areas: Salesforce + CRM features, Slackbot AI capabilities, and admin/productivity improvements. Here's the full list at a glance.
| # | Feature | Plan availability | Admin action? |
|---|---|---|---|
| 1 | Private Salesforce channels | Salesforce channels customers | Optional — new visibility mode |
| 2 | Slackbot: Salesforce actions | Slack CRM / Salesforce channels | Yes — configure object write access |
| 3 | Slackbot list creation and management | Enterprise+ and Business+ (v2) | No |
| 4 | Slackbot web search | Enterprise+ and Business+ (v2) | Yes — off by default, must enable |
| 5 | Today view (beta) | Beta opt-in | Yes — admin opt-in |
| 6 | Focus mode | All members | No |
| 7 | Workflow managers can edit/delete workflow messages | Workflow Builder users | Optional — manage permissions |
| 8 | Auto-log emails/calendar with Einstein Activity Capture | Business+ with Slack CRM | No — member self-serve |
| 9 | Send emails to leads and contacts from Slack | Business+ with Slack CRM | No — member self-serve |
| 10 | Temporarily mute channels | All members | No |
| 11 | Internal Slack links display as titles | All members | No |
| 12 | Flag content expands to channel names/topics | Enterprise plans | Auto-enabled if flagging is on |
Four items in this update deepen the Slack–Salesforce connection, reinforcing Slack's role as a working surface for CRM data.
Salesforce channels now support a new Private visibility mode, in addition to the existing Limited access option. This gives teams tighter control over who can see deal- or account-linked conversations — useful for sensitive opportunities, M&A work, or regulated client discussions. See Slack's guide to setting up and managing Salesforce channels.
Slackbot can now create and edit Salesforce records directly in Slack. Members review changes in an interactive draft card before anything is saved, admins configure which Salesforce objects allow write access, and every action is attributable in audit logs. This is a meaningful governance design: AI-assisted record updates with human review and a clear audit trail. Details are in Slack's article on viewing and updating Salesforce data in Slack.
On Business+ plans, Slack CRM members can connect a Google account so emails and calendar events sync automatically to Salesforce records via Einstein Activity Capture. Members opt in themselves — no admin setup is required. This closes one of the most common CRM data-quality gaps: unlogged activity.
Also on Business+, members with a Slack CRM license can compose and send emails to Salesforce leads and contacts directly from Slack. Like activity capture, this is self-serve with no admin configuration.
Why this matters: taken together, these features let a rep work an entire deal motion — conversation, record updates, email, and activity logging — without leaving Slack. That raises the stakes on getting object permissions, channel strategy, and data governance right.
Three Slackbot capabilities shipped, with different defaults worth noting.
Slack previewed five capabilities. Note Slack's own disclaimer: forward-looking functionality is subject to change, so don't make purchase decisions based on these items alone.
Two items in this update carry hard dates. Treat both as action-required.
| Item | Deadline | Who acts | What to do |
|---|---|---|---|
| Windows .exe installer deprecation | March 2027 | IT / endpoint teams | Transition new deployments to the MSIX package |
| FedRAMP support-data change | August 19, 2026 | Slack Primary Owner | Submit request if support data must stay in the FedRAMP boundary |
The legacy Squirrel-based .exe installer will no longer be downloadable after March 2027, and no new releases will ship for it. IT teams should transition new deployments to the MSIX package, which supports enterprise deployment features and modern auto-update. Existing .exe installs keep working and auto-updating — this only affects new deployments. Slack's deployment guidance is in Deploy Slack for Windows — legacy installers.
Suggested timeline: inventory current Windows deployment methods now, pilot MSIX in Q3–Q4 2026, and standardize all new images and provisioning on MSIX well before March 2027.
Slack support cases and support communications are moving to Salesforce's commercial support infrastructure, outside the FedRAMP authorized boundary. This does not affect workspace data. If your organization requires support data to remain within the FedRAMP boundary, your Primary Owner must submit a request before August 19, 2026. Details are in Slack's FAQ on changes to FedRAMP for Slack support data.
For broader retirement tracking, bookmark Slack feature and plan retirements and the Slack Help Center.
A practical checklist for this release:
If your team is evaluating how these Slack changes apply to Salesforce workflows, integrations, or CRM governance, Vantage Point can help assess the right next step and build a practical rollout plan.
Slack is becoming a primary front end for Salesforce work — and that only pays off when channels, record automation, permissions, and adoption are designed intentionally. Vantage Point is a boutique, senior-led consulting partner that helps teams:
Ready to operationalize Slack and Salesforce together? Talk to Vantage Point about your Slack + Salesforce roadmap.
The biggest changes are private Salesforce channels, Slackbot Salesforce actions (create and edit records in Slack with admin-controlled object access), Slackbot web search (off by default), self-serve Slack CRM email and activity logging on Business+, and two deprecations: the Windows .exe installer (March 2027) and the FedRAMP support-data change (request deadline August 19, 2026).
No. Slackbot web search ships disabled, and an admin must explicitly enable it in Slackbot access and settings on Enterprise+ and Business+ (v2) plans. Review your data-handling and acceptable-use policies before turning it on.
Existing .exe installs keep working and auto-updating. The change affects new deployments: the legacy Squirrel-based .exe will no longer be downloadable after March 2027 and will receive no new releases, so IT teams should standardize new deployments on the MSIX package before then.
Slack support cases and communications are moving to Salesforce's commercial support infrastructure outside the FedRAMP authorized boundary. Workspace data is not affected. If your organization requires support data to stay in the FedRAMP boundary, your Slack Primary Owner must submit a request before August 19, 2026.
Yes. Slackbot can create and edit Salesforce records inside Slack, with members reviewing changes in an interactive draft card before saving. Admins control which Salesforce objects allow write access, and all actions are attributable in audit logs.
No. On Business+ plans, Slack CRM members can self-serve: they connect their Google account so Einstein Activity Capture auto-logs emails and calendar events to Salesforce records, and licensed members can also send emails to leads and contacts directly from Slack. Admins should still communicate the features so adoption is consistent.
The Slackbot MCP client (coming soon to Enterprise+) lets Slackbot connect to external tools and data sources via the Model Context Protocol. Admins must approve MCP servers before members can connect to them via OAuth, so governance planning should start before rollout.
Vantage Point helps teams operationalize Slack and Salesforce together — Salesforce channel strategy, Slackbot record-action permissions, workflow automation, integration, and governance — through senior-led advisory and implementation services. Start with a conversation about your current Slack + Salesforce workflows.
Note: Slack's announcements about future functionality are forward-looking and subject to change; make adoption decisions based on features that are generally available.