You will learn how Slackbot and Claude Tag differ in access, billing and admin control, and what to set up before users start tagging Claude.
Why read this
The piece gives a practical rollout checklist for Salesforce admins.
Channel or group DM
Uses tools set up for the channel
Runs under Claude's own identity
Billed to your organization
One-to-one DM or AI panel
Uses the user's own Claude account
Uses that user's own connectors
Billed to that user's account
Where a user messages Claude decides whose access and billing apply
Claude is now the default model for Slack, powering Slackbot and supporting team work through Claude Tag. The two experiences work differently and each has its own admin controls, so the article sets out what each does, who manages it, and what to check before users begin tagging @Claude.
Slackbot needs no installation. Recent August 2026 upgrades include Big Mode for drafting long documents, Deep Research that returns cited reports from org data and the web, Skill Sets that can be shared and assigned to groups or channels, a Skills Admin Dashboard showing usage, and a Tasks tab for recurring routines. Feature availability depends on rollout timing, licensing and extra license requirements, and compute-heavy Advanced Features are limited at Enterprise+ with 30 days’ notice before any new limits.
Claude Tag, Anthropic’s product, places Claude in channels as a shared teammate, replacing the older Claude in Slack app. It is in beta and requires a Claude Team or Enterprise plan. Whose access it uses and who pays depends on where the user messages it: channels use the tools set up for that channel and bill the organization, while one-to-one DMs use the user’s own account. Setup needs a Slack workspace admin to install the app and a Claude Owner to pair the workspace and set spend limits. Owners control access by workspace or channel, guest channel access (restricted by default), spend caps with alerts at 75% and 90%, and auditing of scheduled work and memory on the Activity page. Slack conversations are kept apart from Claude chat history and deleted within 30 days of disconnecting.
The article closes with a rollout checklist: confirm the roles, pilot a low-risk channel, scope connections by channel, set spend caps first, keep guest access restricted, check the Slack plan, review Skill Sets, and teach users when to use a channel versus a direct message.
You will learn what a custom MCP server needs before Slackbot can render HXL widgets, how to connect Slack through the Salesforce Org Connection, and how to set tool permissions and descriptions so the right tool is chosen.
Why read this
You will also see how to troubleshoot a missing card.
Check the MCP server definition
Map users by Federation ID
Request and approve the org connection
Add the MCP server in Slack admin
Turn on the server and set tool permissions
Steps to make an HXL widget appear in Slackbot, in the order the article gives them
The article explains how to make an existing HXL widget appear in Slackbot. If a widget already renders in Claude or ChatGPT, it can render in Slackbot without changes to the widget, the Apex action or the Custom Lightning Types. The remaining work is configuration: deciding how Slack connects to the Salesforce MCP server, who can use it, and which tools Slackbot may run. The author uses the Pronto sample app to show a storefront card and a follow-up menu card.
Before connecting, the server must be active, every resource needs a description, each tool’s uiResource must match a resourceName, and each tool’s readOnly and destructive flags must be set. Slackbot treats unclassified tools as write tools, which adds confirmation prompts. The connection itself is made through the Salesforce Org Connection: users are mapped by Federation ID, the org is requested and approved from Slack and Setup, and the MCP server is added in Slack admin and confirmed by a Date added value.
Each user then turns on the server in Slackbot and approves tools, choosing Allow once, Always allow or Deny per tool. Two limits apply: up to five active servers per user, and a 60-second timeout per call, with stateless calls that rerun the Apex action, so calls should stay small. Overlapping tools on other servers or Slackbot’s own Salesforce search can cause a plain table instead of the card, so descriptions should be specific.
The troubleshooting section maps common symptoms, such as plain text, missing tools, or blank values, to causes and fixes. Testing with a debugging tool like MCP Inspector helps separate server definition problems from Slack problems.
By Rabia Daud and Libby Knell · Salesforce BlogYou will also see how admins scope agents and users, and how alerts are created and managed through Slackbot.
You will learn the setup path for Tableau Next's three proactive features: autonomous insights, data alerts and intelligence briefs.
Why read this
You will also see how admins scope agents and users, and how alerts are created and managed through Slackbot.
Set up Tableau Agent in Tableau Next
Connect Slack to Salesforce
Enable Tableau Next MCP server for Slackbot
The one-time admin setup that connects Tableau Next to Slack and MCP
Proactive Intelligence in Tableau Next has Tableau Agent monitor business data in the background and push prioritized insights to Slack, Salesforce or any MCP-compatible client. The article describes three capabilities that work together: autonomous insights, which explore data for risks nobody thought to ask about; data alerts, which notify on conditions such as a commit drop or a large deal slipping; and intelligence briefs, which run scheduled or on-demand reviews of core KPIs. All three draw on the governed semantic model so calculations follow the organisation’s definitions.
Setup is a one-time admin task. Prerequisites are Tableau Next in Enterprise, Performance or Unlimited edition, at least one AI-ready semantic data model, and Slack with the Salesforce app and Slackbot connected to MCP. The admin sets up a Tableau Agent, connects Slack to Salesforce, and enables the Tableau Next MCP server for Slackbot. For autonomous insights, the admin turns on the feature under Administration settings, scopes the agent to semantic models, creates an Agentforce Studio skill that supplies business context without scripting output, grants the AI Skill User Permission Set, and assigns an agent to each user, since no one receives insights until that step is done.
Alerts can be created in plain language through Slackbot, or through built-in metric alert types such as period-over-period change, unusual change, goal and threshold. Alerts check daily or weekly and notify only when the condition is met. The article recommends a phased rollout: start with one key alert, pilot autonomous insights with a small group of leaders, then automate one recurring review with an intelligence brief.
You will learn how to connect your Salesforce org to Slack and configure the Slackbot UI system permission so users can access the agent directly in Lightning Experience.
Connect Salesforce org to Slack workspace
Create a Permission Set for Slackbot
Enable the Slackbot UI system permission
Assign the Permission Set to users
The setup sequence for giving users access to Slackbot in Salesforce Lightning
The article outlines the configuration steps required to make Slackbot available inside Salesforce Lightning Experience. Before any user-facing features can be enabled, administrators must link their Salesforce org to a Slack workspace through the Manage Slack Connection setting and accept the pending request.
Access is controlled via a dedicated system permission called Slackbot UI. Administrators create a Custom Permission Set, navigate to System Permissions, check the box for the Slackbot UI capability, and save the changes. The Permission Set is then assigned to individual users or groups who require access.
Best practices emphasize validating the connection in a Sandbox first, using a dedicated Permission Set for easier auditing, and setting assignment expiration dates for pilot phases. The guide also notes that using Slackbot may require Flex Credits approval from a Salesforce administrator, and recommends verifying that the agent respects existing object and field-level security before full deployment.