One admin connection turns on Salesforce inside Claude for every seller

A seller opens Claude on a Monday morning and, before typing anything, sees their own accounts. Salesforce says the plugin's onboarding reads a seller's context out of Salesforce, Slack and any other connector already in Claude. It then stands up a tailored dashboard with their accounts, pipeline and live data in interactive views Claude generates ^[4].

Setup is a single admin action. One connection, with authentication and permissions managed centrally, and every seller on the team live from day one. Salesforce's own copy promises no per-user setup, no new permissions model to build and no re-auditing account by account ^[6]. Salesforce also says actions taken from Claude route back through Salesforce so business rules are enforced whenever an action is taken ^[5]. Put those together and the permission sets already sitting in the org decide what Claude may write to an opportunity. A permission set that was loose but harmless when a human had to click through three screens is still loose when a skill does the clicking.

The skills are the part a buyer has to price out. The announcement names three of the 37: meeting prep, deal health review and pipeline review ^[3]. The remaining 34 are not itemised ^[7]. Salesforce says the skills were built by Salesforce and Anthropic and engineered to draw on Claude's reasoning, agentic tool use and generative UI. It calls them "not generic CRM prompts wrapped around an API" ^[8]. That is a reason to expect them to behave better than a wrapper, and a reason they do not follow a team that moves to a different assistant next year.

Underneath sits AIforce, which Salesforce describes as a harness that brings business data and workflows to any agent through MCP servers, APIs and CLI tools ^[14].

Marc Benioff, Salesforce's chair and CEO, said: "Here, the UI is the AI - allowing you to build custom apps dynamically and answer any enterprise question." ^[10] Dario Amodei, Anthropic's CEO and co-founder, said companies "can point Claude at the customer information and business context that they've been building in Salesforce for decades, and use it to actually run and grow their businesses." ^[12] The release adds that for decades enterprise software required users to manually navigate static UI ^[13].

The work here is local, and it comes before an admin clicks connect. Part of it is the permission sets your sellers already carry, and which of those you would hand to a skill that runs without a human reading each screen. The rest is a comparison: the deal health review skill against one live opportunity, the same review by hand, then what landed in the record next to what the field history says about who changed it. If the writes match and the history names an actor you can trace, this is an interface change for your sellers. If they do not match, it is a change to how your org is governed, and it needs an audit plan before the access switches on for everybody at once.