The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Setting claude's read and write limits in Salesforce through tool restrictions (opens in a new tab)

You will know how the Sales Cloud in Claude plugin reaches Salesforce, why user permissions set what Claude can read, and how the Dispatch tool restriction setting controls whether Claude can create or update records.

Why read this

You will also have a staged rollout plan with a pre-pilot permission review.

  1. Review permissions before the pilot
  2. Set Dispatch to Deny for read-only
  3. Move to Needs Approval for writes
  4. Use Always Allowed only as last step
Salesforce recommends stepping from read-only to approval-gated writes in this order

Sales Cloud in Claude gives sellers a sanctioned way to ask Claude about their Salesforce accounts. The connection runs as the seller, using their own permissions, against live Salesforce data. The Sales Cloud in Claude plugin, built by Salesforce and Anthropic, bundles 37 sales skills, the Salesforce MCP connection and a setup skill that tailors the plugin to each user’s role. The plugin is in beta and requires an enterprise agreement with Anthropic and Sales Cloud licenses.

The plugin works through the standard Salesforce Hosted MCP Server, which exposes Discover, Describe, Dispatch read-only and Dispatch tools. A Salesforce Admin sets up the server and an External Client App, and the Claude admin configures the connector, sets tool restrictions and decides who gets access. When a seller signs in through OAuth, requests run with that user’s credentials, so field-level security and Sharing Rules apply. Reads need no approval, while writes depend on the Dispatch setting.

Because the hosted server has no generic system user, a user’s object permissions, field-level security and Sharing Rules define what Claude can reach. Those permissions were designed for a human, so broad grants such as View All and Modify All may give Claude more than the job needs. Data Claude reads is also sent to the connected model, which makes the review a data-sharing decision as well as a security one.

The Dispatch tool restriction, found under Organization Settings > Connectors, has three options: Needs Approval, which Salesforce recommends as the steady state; Always Allowed; and Deny, which keeps Salesforce read-only. Dispatch can also call deletes directly even though no skill deletes, so Deny or Needs Approval matters. Salesforce suggests a staged approach: clean up permissions before a pilot, agree the Dispatch setting with the Claude admin, then pilot with a small group and review early approvals. Record each decision in an architectural decision record.

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

Worth reading?

Recommended

AIforce exposes Salesforce configuration to outside agents through MCP and the Headless Toolkit (opens in a new tab)

You will learn what AIforce and the Headless Toolkit expose from your org, the five tools that make it up, and how the security model applies to agents acting as users.

Why read this

You will also see what admins should review before opening the org to external agents.

Headless Toolkit

  • MCP servers
  • APIs
  • Skills
  • Plugins
  • Developer tools
The Headless Toolkit has five parts that expose org configuration outward

Salesforce’s AIforce strategy lets people work with Salesforce from the tools they already use, such as Slack, Claude and other AI clients, rather than only from the Salesforce UI. The article places AIforce as the interface layer above Data 360, Customer 360 and Agentforce. It stresses that the Lightning UI, Reports and Dashboards are not going away.

The Headless Toolkit, formerly called Headless 360, is the set of technologies that makes this work. It has five parts: MCP servers, which use OAuth and may be Salesforce-hosted or custom; APIs, including the Agent API and the platform data APIs; skills, which are instruction folders that AI clients load for a task; plugins, which package skills with commands and MCP connections; and developer tools such as the Salesforce CLI, Agentforce Vibes and the declarative Agent Script format. The article says this is an umbrella over existing capabilities rather than a new product, citing 60+ MCP tools, 4,000+ APIs and 220+ CLI commands.

For developers building external applications, there are two routes: the Headless Experience Layer, which renders workflows natively in channels such as Slack, WhatsApp, voice or mobile, or direct calls to the APIs and MCP tools with a custom UI. Either way, the flows, data models and guardrails configured in the org are what they build on.

On security, the article says Sharing Rules, field-level security and Permission Sets are respected however data is accessed, and that calls pass through the Trust Layer. Every call carries identity, access, capability and governance controls, so Validation Rules, triggers and governor limits still apply. Because an agent can do anything the acting user can do, the article advises reviewing profiles and Permission Sets before exposing the org. Agentic Identity, where agents have their own permissions and credentials, is described as planned for the near future.

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

Worth reading?

AIforce is a separate Layer from Agentforce, and developers shift to design and review (opens in a new tab)

You will learn how the Headless Toolkit and AIforce differ from Agentforce, and how the developer role is shifting toward guidelines, review and guardrails.

Why read this

The piece is a session recap rather than a technical guide.

Headless Toolkit

  • MCP Servers
  • Headless Experience Layer
  • Multi framework support
The Headless Toolkit has three pieces that together open Salesforce to any agent

The author writes that AIforce does not replace Agentforce. Agentforce remains Salesforce’s own AI, while AIforce is the layer that opens Salesforce to any MCP client or agent, together with partnerships with agent vendors. He lists the Headless Toolkit’s parts: MCP Servers that expose business logic to any agent, a Headless Experience Layer that renders interfaces dynamically inside agents, and support for frameworks such as Angular and React alongside Lightning Web Components.

According to Alba Rivas of Salesforce, as cited in the piece, the classic workflow of creating objects, writing queries, classes, tests and deploying has less time left. The developer’s work moves to design (asking an agent for a solution that follows your guidelines), review (checking that output matches the request), and guardrails (giving the agent knowledge and limits). Building an app that works in a production enterprise environment is the hard part.

The piece also notes that the Claude relationship continues with an existing Salesforce plugin, while OpenAI and NVIDIA also appeared on stage. It describes MCP as becoming a universal protocol used by business users too, and skills as Markdown files that can be shared across a team.

Read the original at dev.to (opens in a new tab)

Worth reading?

Skills admins need to build with AIforce's MCPs, Skills and Plugins (opens in a new tab)

You will learn how MCPs, Skills and Plugins fit together in the AIforce extensibility stack and which new admin skills to pick up first.

Why read this

It gives a roadmap and the training trails to follow.

  1. User triggers a Plugin
  2. Skill fires
  3. MCP executes
  4. Output returns to user
How the AIforce building blocks work together when a user acts

The post introduces AIforce as a new layer of the AI extensibility stack and explains three building blocks. MCP, the Model Context Protocol, is a standard bridge between an AI interface and live systems, data and APIs, so admins can expose flows, APIs and Apex without writing custom code for each system. Skills define the exact steps, rules and formatting an AI needs to complete a task consistently, and Plugins package MCP connectors, Skills and interfaces into a single installable product. It describes a flow in which a user triggers a Plugin, a Skill fires, an MCP executes and the output returns to the user.

The author lists the new admin skills to develop: MCP management, including centralised org-wide connections and Agentic Identity; building deterministic agent logic with Super Agents and Subagents; lifecycle management of Plugins mapped to user roles; and using Agentforce Coworker, Agent Script, Builder Central and Agentforce Vibes for AI-assisted building. The roadmap moves from AI Trust, Security and Governance trails through hands-on work with Agentforce Studio to advanced building and packaging, then ongoing change management.

The article is largely an overview with links to trails, workshops and resources rather than technical implementation detail, so practitioners will get orientation more than hands-on specifics.

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

Worth reading?

Salesforce unveils AIforce apps linking platform data to Claude and Slack (opens in a new tab)

You will learn what the three AIforce applications are, what each does with Salesforce data, and what the Claude Code plug-in adds for developers.

Why read this

The piece is a brief overview without implementation detail.

AIforce initial release

  • Claudeforce
  • Slackforce
  • Agentforce Coworker
The initial AIforce release is made up of three applications

Salesforce announced AIforce at Dreamforce, a set of applications that connect platform data and workflows to Claude and Slack. The initial release has three parts: Claudeforce, Slackforce and Agentforce Coworker. Claudeforce comes out of an expanded partnership with Anthropic and ships with 37 pre-installed sales capabilities, from prospecting to opportunity management, plus a Claude Code development add-on with more than 40 further tools. Deloitte, GitLab and Legora piloted it, and it is now in beta for all customers.

Slackforce brings Salesforce data into Slack conversations, letting teams combine information from different sources, apply filters and take actions through interactive surfaces. The upgraded Slackbot assistant and Slack CRM feature can update files and create records from simple text commands.

Agentforce Coworker works inside Salesforce’s internal Lightning environment as a digital assistant that uses customer history and activity. According to the company, it needs no data migration or new permission settings, and it recorded 100,000 activations in its first 35 days.

Read the original at dev.to (opens in a new tab)

Worth reading?

Must-read

Preparing your org for the Claudeforce partnership and new billing model (opens in a new tab)

Readers will learn how to configure the Salesforce in Claude plugin, audit permissions for agentic access, and prepare for the November billing model using Flex Credits and agent registration.

  1. Audit Permission Sets and profiles
  2. Clean the fields the skills read
  3. Keep approvals on
  4. Pilot in a sandbox
  5. Name an owner for connections
Five checks to prepare your Salesforce org for Claudeforce and AIforce billing

Claudeforce, the expanded Salesforce and Anthropic partnership announced on August 26, 2026, works in two directions. Claude becomes a reasoning model inside Agentforce and the default model in Slack, while Salesforce reaches into Claude through the Salesforce in Claude plugin. That plugin bundles 37 prebuilt sales skills covering account research, call prep, pipeline review and CRM updates, with Salesforce and Slack connectors. It is in beta for approved orgs on paid Claude plans and requires the latest Sales Cloud Enterprise edition.

On security, sellers sign in with their own Salesforce credentials, so Claude can only do what their permissions allow, and by default it asks for approval before any write. Salesforce Help notes that when a custom action uses a Claude model hosted inside the Salesforce Trust Boundary, data stays inside that boundary, though Einstein Trust Layer data masking is disabled for those agents and zero data retention still applies. The article advises reading that page in full before writing a risk assessment, and it warns that most capability claims come from launch material and should be tested in a sandbox first.

The setup path has four stages. First, the org confirms eligibility and gets approval through the beta sign-up on AgentExchange. Second, a Salesforce admin creates an External Client App for Claude, because Connected Apps are not supported for MCP clients. Third, a Claude Primary Owner or Owner enables the plugin in Organization settings and enters the app’s consumer key and secret. Finally, each member signs in with their own Salesforce account on first use.

The billing changes are targeted for November. Admins register agents, each of which gets its own identity and can hold a narrower Permission Set than a human user. Every successful MCP or API call from a registered agent counts as a Headless Platform Interaction, paid with Flex Credits, though the rates are still TBA and metering applies only to active production orgs, with 30 days’ notice before it starts. Customers who buy on or after September 17, 2026 must register agents at purchase, while existing customers register at renewal. The article does not say how the Salesforce in Claude plugin will be classified under this model.

The article recommends five preparation steps: audit Permission Sets and Profiles, clean the fields the skills read, keep approvals switched on, pilot in a sandbox, and name an owner for connections and consumption. Cloud Odyssey’s own view is that Claudeforce exposes existing CRM data quality problems, and it suggests starting with a health check, connecting surrounding systems, piloting with one team, and keeping model choice open.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Agentforce Coworker setup, security and routing within AIforce (opens in a new tab)

It explains how Agentforce Coworker fits into the AIforce stack, how its routing and security model work, and gives a concrete setup path via Data 360 and Salesforce Go.

Agentforce Coworker is presented as one of three main pillars of AIforce, Salesforce’s interface layer announced at Dreamforce ’26. Its purpose is to bring Salesforce data and agents to where users already work, such as Lightning Experience, Slack, Microsoft Teams or AI tools, instead of making them switch between applications. It targets two problems: tab-switching between many tools, and users struggling to know which agent to use for a task as agentic workforces grow. It acts as a router agent, the front door to an org’s agents, sending queries to the right one. Its foundations are Agentforce (the digital workforce layer it orchestrates), Customer 360 (CRM as the unification point for customer data) and Data 360 (the grounding layer that indexes and governs data for AI).

The piece describes three interaction modes. Find lets users ask questions in plain language and get contextualized answers drawn from CRM data, Slack, files, knowledge bases and other connected sources. Catch Up proactively surfaces changes in the user’s scoped workspace, such as what they missed while in meetings. Plan and Act takes outcome-level instructions and routes the work to the appropriate agent. Security relies on the existing Salesforce model: profiles, Permission Sets and Sharing Rules still apply, so Coworker only sees what the user is allowed to see, following least privilege.

The author’s hands-on setup path begins with confirming Data 360 is enabled, checked under Data Cloud Setup Home, and assigning the Agentforce Coworker Admin Permission Set to administrators. Coworker is then switched on through Salesforce Go by searching for it in Setup. Administrators choose data sources under Manage Data, with CRM data enabled by default. Finally, users need the Agentforce Coworker User Permission Set, which can be assigned via Manage Access to Agentforce Coworker in Manage Users. In use, the Ask button beside global search opens the Ask: Home tab, and the author recommends starting a fresh session for unrelated prompts to avoid carrying over context.

The article closes with caveats. Data 360 must be enabled before Coworker works, though not every data set must be shared with it. Coworker is available in Enterprise, Unlimited and Agentforce 1 Editions. Billing is either consumption-based through Flex Credits or seat-based with usage caps, so costs can rise quickly and the author suggests monitoring value with tools such as Agentforce Grid and Agentforce Observability. The author also advises planning and cleaning data and permissions before rollout.

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

Worth reading?