Build1 publisher2 min readPublished
Claude's Salesforce beta proposes changes like close-date updates for sellers to approve
Anthropic's 37-skill beta reads only what a user's Salesforce permissions allow and writes back only after that seller approves each change. The approval is a default setting. Revenue teams now have to govern it.
The Engineer · Build desk

What happened
- Anthropic launched Salesforce in Claude on September 15th, giving the assistant access to accounts, opportunities and pipeline data while Salesforce stays the system of record.
- Claude gathers context from Salesforce, Slack, email and call transcripts, then proposes record changes such as moving a close date, adding a contact, logging a call or creating a follow-up task.
- The integration runs under each user's existing Salesforce credentials, reads only records that user may access according to Anthropic, and leaves Salesforce's business rules governing the actions.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- constraint Inherited Salesforce permissions bound which records Claude can reach, and that layer checks access alone, so a buyer cannot treat access control as write control.
- decision The group list an administrator picks becomes the boundary of who can move revenue records with an agent's help.
- cost The plugin has no separate price, so the cost of a pilot is administrator time to connect the org plus the review minutes each proposed change takes out of a seller's day.
- exposure Approval is described as a default, so whoever controls that setting controls whether agent writes into forecast fields stay human-gated.
A write goes into Salesforce as the signed-in user. Anthropic says Claude reads only the records that user is permitted to see, and that Salesforce's business rules still govern actions taken through the integration [5]. Validation rules and field-level security apply to a proposed edit the way they apply to a manual one. That answers whether the seller may change the close date.
The accuracy check is the approval. Sellers approve proposed changes by default before Claude writes them back, according to Anthropic [4]. A default is a setting. Anthropic did not say who can change it, whether it can be relaxed for some skills, or whether an administrator can switch it off for a group.
Approval sits with the seller, and the seller's records feed the manager's numbers. Claude builds the pipeline view with coverage by stage and likely deal slippage, and drafts forecast narratives in the sales organisation's preferred format [11]. Moving a close date is one of the writes it proposes [3]. In my view a per-seller approval is the wrong grain for amount and close date, because the person clicking approve is the person whose coverage improves. I would route approvals on those two fields to the manager who owns the forecast.
The justification for an edit is assembled outside the system of record, from Slack, email and call transcripts [3]. The seller clicking approve sees the summary. They may not open any of the three.
Anthropic's announcement names GitLab, Siemens and Legora as deployments and puts 7,000 Salesforce sellers on the plugin [9]. That counts users, not accepted proposals. For the figure to say anything about the approval design, it would have to come with a rejection rate: the share of proposed writes that sellers edited or refused.
Turning the plugin on belongs to an administrator, who requests access through Salesforce's AgentExchange and connects Salesforce at the organizational level [7]. Individual users have no route to switch it on themselves [16]. Salesforce said in August that the integration was available to select pilot customers, with open beta planned for September [12], and the September 15th launch fell inside that window [13].
In a 2023 interview with Stripe, Anthropic president and co-founder Daniela Amodei said the company's founders wanted to make AI safer "from day one" and keep humans at the center of how the technology is deployed [14]. Salesforce keeps ownership of the records, permissions and workflow rules, and Claude is another interface to them [17].
What to watch
- The scope of the approval setting, if Anthropic spells it out: per user, per skill, per group, and who is allowed to change it.
- A published rejection rate on Claude-proposed writes, or any independently measured result from GitLab, Siemens or Legora.
- What Salesforce's audit trail records alongside a Claude-originated write: the field change alone, or the transcript that justified it.