Slack July 2026 Admin Updates: Key Changes and Deadlines

Slack (a Salesforce company) published its July 2026 Admin Updates on July 8, covering new Slackbot capabilities, Salesforce data now inside Slack, and three deprecations admins need to plan around. The two most time-sensitive items are a FedRAMP boundary change for support data — with an August 19, 2026 action deadline for regulated organizations — and Salesforce Tasks and Events now working directly inside Slack, which most teams can start using immediately with no setup required.

This guide breaks down every change in the July update, organized the same way Slack organized its newsletter: What's New, Coming Soon, and Upcoming Deprecations. Each deprecation includes a plain-language "what you need to do" action item and a deadline, so admins can prioritize without re-reading the original email.

This is written as a general reference for Slack and Salesforce admins at any organization. It does not reference any specific customer, workspace, or org ID.

Quick Answer

What it is: A summary of Slack's official July 2026 Admin Updates — new Slackbot features (MCP client, memory, charts, voice), Salesforce Tasks and Events inside Slack, org-level user groups, an admin awareness banner, app access control lists, upcoming features, and three deprecations with deadlines. Who it matters for: Slack Org Owners, Admins, IT and security teams, and Salesforce admins managing Slack-Salesforce integration. What it helps you decide: Which changes require immediate admin action, which are safe to roll out gradually, and which deprecations affect your infrastructure or compliance posture. Why Vantage Point is relevant: Vantage Point is a senior-only Salesforce and Slack consulting partner that helps teams govern new Slack and Slackbot capabilities, connect Salesforce data into Slack workflows, and stay ahead of platform deprecations.

TL;DR

What's in the July 2026 Slack Admin Update?

Slack's monthly Admin Updates newsletter tells Org Owners, Admins, and IT teams what changed, what's coming, and what's being deprecated across the platform. The July 2026 edition covers 12 "what's new" items, five upcoming features, and three deprecations — the most notable being a FedRAMP-related change to where Slack support data lives.

The table below summarizes every item and who is affected, so you can jump straight to the sections relevant to your organization.

What's New in July 2026

Slackbot MCP client (Enterprise+ and Business+ v2)

Slackbot can now connect to apps your team already uses through the Model Context Protocol (MCP), an open standard for connecting AI assistants to external tools and data. Once an admin installs an app that includes an MCP server, anyone with Slackbot access can start a conversation and have Slackbot interact with that tool directly. The Slack Marketplace MCP Registry lists every third-party MCP server available to install.

Admin action: Existing apps must be updated before members can authenticate and use MCP inside Slackbot. Review the guide to Model Context Protocol in Slack and treat MCP-enabled apps like any other privileged integration — approve deliberately and scope access tightly. If your organization worked through the Slackbot MCP Client rollout in June, this July update is the natural next step: updating existing apps rather than installing new ones.

Slackbot memory (Enterprise+, Business+ v2, Business+ v1, and Enterprise Grid with Slack AI add-on)

Slackbot can now retain preferences and context across conversations, so members no longer have to repeat instructions in every session. Users can view, correct, or delete anything Slackbot has saved about them at any time, which keeps the feature transparent and auditable from an end-user perspective.

Slackbot charts (same tiers as memory)

When a member asks Slackbot to visualize data, it can now render line, bar, pie, and area charts directly inline in the conversation instead of describing the data in text.

Slackbot voice dictation (same tiers as memory)

Members can now use one-way voice input to talk to Slackbot instead of typing, which is useful for quick requests from mobile devices or hands-busy situations.

Improved Workflow Builder error messages and activity log

When a workflow fails, builders and end users now see a specific, actionable error message instead of a generic failure notice — including the error type, the step that failed, and guidance on how to fix it. The Activity Log also now shows this error detail inline, which should meaningfully cut troubleshooting time for admins who maintain a large library of workflows.

Salesforce Tasks and Events now supported in Slack

This is one of the most immediately useful changes in the update. Salesforce Tasks and Events can now be viewed, edited, and acted on directly inside Slack — in list views, record views, Salesforce Channels, record card unfurls, and through Slackbot AI. It works across desktop, iOS, and Android.

For sales and service teams already living in Slack, this removes a common context-switch: no more flipping to Salesforce just to check or update a task tied to a deal or case. If your organization already uses Salesforce Sales Cloud or Service Cloud alongside Slack, this is worth testing with a pilot team this month.

Organization level user groups (Enterprise plans)

Org Owners and Admins can now make identity provider (IDP) groups and Admin groups visible in Slack, so they can be used for mentions and channel invites without duplicating group management work. See Slack's guide on managing user groups from the admin dashboard for setup steps.

Naming group DMs

Members can now give group direct messages a custom name instead of relying on the auto-generated list of participant names — a small but frequently requested usability fix.

Slackbot analytics dashboard (Enterprise+ and Business+ v2)

Admins now have a dedicated Slackbot Analytics page in the org dashboard, giving visibility into Slackbot usage and adoption across the organization. This is a useful data point for justifying (or right-sizing) AI add-on spend and for identifying teams that need more enablement.

Moving Slack system DMs out of Slackbot

Slack is migrating roughly 180 system alert notification types — archived channels, canvas access changes, Workflow updates, and similar system events — out of Slackbot direct messages and the Activity feed. These will now arrive from a new, dedicated "Slack" system user. No admin configuration is required; this is a naming and routing change that should reduce confusion between AI-generated Slackbot responses and automated system notifications.

International Data Residency for Sweden

Sweden is Slack's newest International Data Residency (IDR) region for storing user-generated data at rest in-region. This helps organizations meet policy, contractual, or regulatory data-location requirements without changing the day-to-day Slack experience. Details are in Slack's data residency documentation.

Admin awareness banner in the organization home dashboard

A new rotating banner on Org Home surfaces productivity apps that aren't yet installed — starting with Google Calendar — along with usage insights tailored to the organization and a single-click install option. This is a low-effort way to close gaps in tool adoption that admins might not otherwise notice.

App access control lists (Enterprise+ and Enterprise Grid)

Previously, once an app was installed, it was available to everyone in the workspace by default. Admins can now restrict which members, IDP groups, or user groups can access a specific installed app — controlling whether they can message it, discover it, or use it as an MCP server in Slackbot. This is a meaningful governance upgrade, especially as more apps double as MCP servers with action-taking permissions.

Admin action: Review your current app install list and consider applying access restrictions to sensitive or high-privilege apps, particularly any that also function as MCP servers.

Coming Soon

These features are announced but not yet generally available. Per Slack's standard disclaimer, purchase of Slack services is not dependent on future functionality, and any of the following is subject to change.

• Compact external link unfurls — link previews shift from full-size cards to a compact, structured format so conversations stay easier to scan.
• Accessibility improvements for select components — better keyboard and screen reader support across Basic Select, Search Select, and Multi Select components.
• Slackbot deep research (Enterprise+, Business+ v2, also Business+ v1/Enterprise Grid with AI add-on) — multi-source investigation of complex questions, beyond simple information retrieval.
• Generate slides with Slackbot (Enterprise+, Business+ v2) — members will be able to describe a presentation in plain language and get a designed deck as a Google Slides file or downloadable .pptx.
• Third-party knowledge sources for AI Generate Response (Enterprise+, Business+ v2, also Business+ v1/Enterprise Grid with AI add-on) — the Workflow Builder AI step will be able to reference Google Sheets, Google Docs, and Salesforce as external knowledge sources.
• Custom sections for files — members will be able to organize starred canvases and lists into custom sections in the Files tab sidebar.

Upcoming Deprecations — Action Required

Each of the following changes has a real deadline. Review them now rather than waiting for the follow-up reminder email.

Changes to FedRAMP coverage for Slack support data — deadline August 19, 2026

Slack is moving customer support data — support cases and related communications — to Salesforce's commercial support infrastructure, which sits outside a FedRAMP-authorized boundary. This does not affect Slack workspace data itself, only support case data.

What you need to do: If your organization requires its support data to remain within a FedRAMP boundary, your workspace's Primary Owner must submit a request before August 19, 2026. Organizations that don't have a FedRAMP-boundary requirement for support data don't need to take any action. See Slack's GovSlack and FedRAMP compliance documentation for background on Slack's FedRAMP posture, and contact your Slack account team directly to submit the boundary request — this is a compliance decision that should involve your security and legal stakeholders, not just IT.

Deprecation of the .exe installer for Windows — March 2027

Slack is discontinuing the legacy Squirrel-based Windows .exe installer. After March 2027, the downloadable .exe file will no longer be available on Slack's download page, and there will be no new releases of this installer package.

What you need to do: IT teams should transition new Windows deployments to the MSIX package, which offers enterprise-grade deployment features and modern auto-updating. Existing installations that were set up with the .exe installer will continue to function and auto-update normally — this change only affects new deployments going forward. Start testing MSIX deployment now using Slack's Windows deployment guide so your imaging and deployment scripts are ready well before March 2027.

OS, app, and browser versions reaching end of support — November 9, 2026

In line with Slack's standard support lifecycle policy, Slack has discontinued support for a number of older operating system, app, and browser versions as of November 9, 2026.

What you need to do: Cross-reference your organization's device fleet and standard browser image against Slack's support lifecycle for operating systems, app versions, and browsers page. Devices on unsupported versions may still be able to access Slack in a degraded state, but should be prioritized for OS or browser upgrades to avoid support and security gaps.

What Businesses Should Do Next

1. Prioritize the FedRAMP decision first. If your organization has any FedRAMP-boundary requirement for support data, get the Primary Owner request submitted well before August 19, 2026 — this is not a default action, so nothing happens unless you ask.
2. Pilot Salesforce Tasks and Events in Slack with one team. This requires no new admin setup and can demonstrate an immediate workflow improvement for sales or service reps who work primarily in Slack.
3. Update apps for the Slackbot MCP client before members ask about it. Treat MCP-enabled apps as privileged integrations and apply access controls before broad rollout.
4. Review app access control lists. If you're on Enterprise+ or Enterprise Grid, use the new access control lists to scope which apps are available to which members, especially apps that also act as MCP servers.
5. Start MSIX testing now, even though the .exe deadline is a year out. IT changes to imaging and deployment take longer to test and roll out than the deadline suggests.
6. Audit your device/browser fleet against the November 9, 2026 support lifecycle page to catch any devices that fell out of support.

How Vantage Point Helps

Vantage Point is a senior-only Salesforce and Slack consulting partner that helps organizations govern new Slack and Slackbot capabilities without slowing teams down. For monthly updates like this one, that typically means:

• Reviewing which Slackbot AI features (MCP client, memory, charts, deep research) make sense to enable, and building the governance and access-control policy around them.
• Connecting Salesforce data — including the new Tasks and Events in Slack support — into a coherent Salesforce and Slack workflow through our Salesforce implementation and advisory services.
• Assessing FedRAMP, data residency, and other compliance requirements against Slack's evolving infrastructure through our compliance and security solutions.
• Managing ongoing platform change, deprecations, and admin backlog through managed services and ongoing support so nothing falls through the cracks between monthly newsletters.

If your team is evaluating how these July changes apply to your Slack and Salesforce environment, Vantage Point can help assess the right next step and build a practical rollout and compliance plan.

FAQ

What is the most urgent item in Slack's July 2026 admin update?

The FedRAMP boundary change for Slack support data is the most time-sensitive item. Organizations that require their support case data to stay within a FedRAMP boundary must have their workspace Primary Owner submit a request before August 19, 2026. No action is needed if your organization doesn't have that requirement.

Do I need to do anything for the FedRAMP support data change if I'm not a government or regulated customer?

No. If your organization doesn't require support case data to remain within a FedRAMP-authorized boundary, this change happens automatically with no action required. It only affects where Slack's support case data (not your workspace data) is stored.

What are Salesforce Tasks and Events in Slack, and do I need to configure anything?

Salesforce Tasks and Events can now be viewed, edited, and acted on directly inside Slack through list views, record views, Salesforce Channels, record card unfurls, and Slackbot AI, on desktop, iOS, and Android. There's no special admin configuration required to start using it if your organization already has Salesforce and Slack connected.

What is the Slackbot MCP client and why do admins need to update apps?

The Slackbot MCP client lets Slackbot connect to external apps through the Model Context Protocol (MCP), an open standard for AI-to-tool connections. Admins must update existing installed apps before members can authenticate and use those apps' MCP capabilities inside Slackbot conversations.

When does the Windows .exe installer stop working?

Existing Slack installations made with the .exe installer will keep working and auto-updating normally — nothing breaks for current installs. After March 2027, Slack will no longer offer the .exe file for new deployments, so IT teams should transition new Windows rollouts to the MSIX package before then.

What happens if my device is on an OS or browser version that lost support on November 9, 2026?

Devices on unsupported OS, app, or browser versions may still be able to access Slack, but in a degraded or unsupported state, per Slack's standard support lifecycle policy. Organizations should prioritize upgrading affected devices to maintain full functionality and security coverage.

How is Slackbot memory different from Slackbot charts or voice dictation?

Slackbot memory lets Slackbot retain preferences and context across conversations so members don't repeat themselves; charts let Slackbot render inline visualizations of data; and voice dictation lets members speak to Slackbot instead of typing. All three are part of the same July 2026 AI feature set available on Enterprise+ and Business+ v2 (and, in most cases, Business+ v1 and Enterprise Grid with the Slack AI add-on).

Where can Vantage Point help with these July 2026 changes?

Vantage Point helps Slack and Salesforce admins decide which new Slackbot features to enable, apply governance and access controls to MCP-enabled apps, connect Salesforce Tasks/Events and other data into Slack workflows, and manage compliance questions like FedRAMP and data residency. Our Salesforce implementation and advisory and compliance and security solutions teams can build a rollout plan specific to your environment.

Related reading: see our guide to the Slackbot MCP Client rollout from June 2026 for background on MCP governance in Slack.