The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Claude becomes Slack's default AI, with two Admin-Controlled experiences (opens in a new tab)

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.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?