The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Salesforce unveils an interface layer to connect platform data and permissions to AI tools (opens in a new tab)

Readers will understand how the new interface layer exposes Salesforce data, workflows, and existing permissions to external and internal AI applications without replacing the core CRM.

Why read this

The piece also clarifies the security model, the role of the Headless Toolkit, and how this capability differs from Agentforce.

Salesforce AIforce is a live interface layer that brings Salesforce data, workflows, business logic, permissions and governance into AI tools such as Claude, Slack and Lightning, so people can query records, update them and trigger workflows without opening the Salesforce app. Announced at Dreamforce, it is positioned as the top layer of Salesforce’s Agentic Enterprise architecture, above Agentforce, Customer 360 and Data 360. The Headless Toolkit, which exposes the platform through MCP servers, APIs, plug-ins and skills, connects these layers. Its three launch surfaces are Claudeforce (Salesforce in Claude, with 37 prebuilt sales skills, now in beta for all customers), Slackforce (Slackbot, Slack CRM and related tools) and Agentforce Coworker in Lightning.

The article explains that AIforce differs from Agentforce: Agentforce builds and runs the agents that do the work, while AIforce is the interface through which people and agents reach Salesforce from outside the app. Coworker bridges the two by calling agents a company has already deployed. On security, the article describes four points: requests run under the user’s existing permissions, hosted MCP servers are inactive until an admin enables them and are logged through Event Monitoring, approval can be required for changes or deletions, and Salesforce says business data is not retained by the model provider under Zero Data Retention. The author advises confirming those terms in the contract, and notes that pricing and availability can change and vary by region.

The piece also covers the naming question: Marc Benioff said on October 9 that AIforce is now SIforce, but Salesforce’s own product pages still used AIforce at the time of writing. It treats the name change as a signal to plan around permissions, data models and integrations rather than brand labels. A case study on BACA Systems, a 50-person manufacturer, describes an Inventory Agent in Slack, a Slack channel per field project, and an ACH payments module that removes card fees, with a projected saving of about $200,000 a year. The article stresses that these are Salesforce-published projections and that BACA’s ERP runs natively on Salesforce, which is unusual.

Finally, the article offers an illustrative scenario for firms whose ERP is SAP, Oracle or NetSuite, where a MuleSoft-style governed API layer is needed to answer cross-system questions. It closes with a six-step readiness checklist (data foundation, permissions, external systems, MCP policy, a single-team pilot, and monitoring) and the author’s view that AIforce amplifies whatever data and permission quality already exists, so organizations should start with packaged surfaces and proof for trust claims before building custom experiences.

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

Worth reading?