Dev tools

Slack Surfaces builds dashboards, decks and reports from a Slackbot prompt, and it is on every plan today

September 11, 2026 at 3:20 AM PT

Salesforce marketing card for Slackforce Surfaces, showing a Slack chat that produces a dashboard

Image: Salesforce

Why it mattersTeams that ship Slack apps or sell dashboards into Slack now have a Salesforce-owned generator in the same channel, and the data used depends on what the user has already granted Slackbot access to.

Salesforce announced Slackforce Surfaces on 10 September 2026. A user asks Slackbot for something in plain language, and Slackbot builds an interactive dashboard, executive presentation, microsite, calculator or a new interface for it, pinned in the channel and open to comments and shared editing from the rest of the team.

What it draws on

Slackbot builds the Surface from the conversation it is in and from whatever else the user has already given Slackbot permission to read. Salesforce lists connected apps like Google Drive and Salesforce records, plus Slack conversations themselves. In the Verge write-up, Ryan Gavin, Slack's chief marketing officer, told the outlet by email that "you're not exporting your data to some other tool to make sense of it, you're asking Slackbot to build the dashboard, the deck, the report right where the conversation already is, and your whole team can act on it together."

Salesforce says the feature will only pull data the user has granted access to. It does not list an audit trail or a governance model on the announcement page, so the guarantee is scoped by whatever Slackbot itself is allowed to see.

What ships and when

The announcement says Slackforce Surfaces is available today for customers on Enterprise+, Business+, Pro, Legacy and Free Teams that have Slackbot enabled for their workspace. That covers every Slack plan, paid or free. The live-data feature, where a Surface refreshes as the underlying records change, begins rolling out in October rather than shipping with the launch.

Salesforce quotes a customer example of a support team tracking cases for 800,000 inquiries a year, and an IT team using a Surface to watch AI adoption and token spend, with a fresh version landing in Slack automatically. The examples are Salesforce's own case-study material.

The consequence for people building in Slack

A category of tool that has been sold into Slack for years, the in-chat dashboard, the poll, the small internal microsite, the survey builder, now has a Salesforce-owned generator sitting in the same channel and driven by the same conversation. Anyone building a Slack integration should read the announcement against their own roadmap and work out which of their features Slackbot has just shipped as a default.

The pattern also matters for teams that maintain a BI or reporting layer. If a marketer or a support lead can ask Slackbot for a dashboard against Salesforce data and a Google Drive folder, the ad-hoc BI ticket may stop arriving on the BI queue and start arriving as a governance question about which data sources any given Slack user is allowed to synthesise into a chart at will.

Source

Source: Salesforce

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

More from AI News

Astral signs and notarizes uv 0.12.12 binaries on macOS and Windows

Astral released uv 0.12.12 on 2026-09-09 with code-signed macOS and Windows binaries, notarized on macOS with an Apple Developer ID and timestamped on Windows with Authenticode.

Source: GitHubDev tools

Polars 2.0 makes the streaming engine the default and stops guaranteeing row order

The Polars 2.0 release candidate switches the default query engine to the streaming engine, which the project warns does not guarantee row order for group-by, join and unpivot.

Source: PressDev tools

Cline Desktop 0.0.26 shows the current branch's GitHub pull request inside the composer, and unifies Tools, Skills and Rules into one list

Cline shipped Desktop 0.0.26 on 11 September 2026, adding a live GitHub pull request view inside the composer, merging the Tools, Skills and Rules panels into a single list, and fixing a set of session and provider bugs.

Source: GitHubDev tools