Salesforce in Claude: what shipped, what it can write, what it cannot govern

TL;DR: Salesforce in Claude is a Claudeforce plugin. The beta opened on 15 September 2026 on paid Claude plans. It puts 37 sales skills on a Salesforce-hosted MCP server so Claude can read pipeline and draft CRM updates. Writes inherit the signed-in user's permissions. The default is ask before write. Salesforce already governs objects, fields, and sharing for that user. A chat that can draft a stage change is still not a versioned RevOps process.

What is Salesforce in Claude?

Salesforce in Claude is the first product from Claudeforce, the August 2026 partnership between Salesforce and Anthropic. It is a plugin for Claude, including Cowork, with 37 prebuilt sales skills. A Salesforce admin connects the org once. Sellers then sign in with their own Salesforce credentials.

The plugin sits on Headless 360: Salesforce capabilities (data, workflows, rules, permissions) exposed over the Model Context Protocol (MCP). Claude does not scrape the Lightning UI. It calls tools.

VentureBeat summarized the press line as Salesforce putting the CRM inside Claude. That is the search query. Here is what actually shipped.

What shipped in the September 2026 beta

Item	What it is
Product	Salesforce in Claude plugin (Claudeforce)
Beta	15 September 2026, paid Claude plans, org admin must connect it
Skills	37 sales skills: account research, call prep, pipeline review, CRM updates, deal scoring, forecast
Transport	Salesforce-hosted MCP, not a homemade connector
Auth	Per-user OAuth. Admin connects the org. Each seller signs in as themselves
Scope	mcp_api plus refresh. Not the full Salesforce api scope
Writes	Inherit that user's object, field, and sharing rules. Default: ask before write
Audit	Salesforce Event Monitoring attributes tool calls to the connected user

Salesforce documents the security model in How to Secure Salesforce Hosted MCP Servers. Use a dedicated External Client App per client. Do not grant the broad Platform API scope. Start with read-only tools if the org is not ready for writes.

Can Claude update Salesforce?

Yes, if the org enabled the plugin and the signed-in user can edit that record.

Claude can draft an opportunity update, a next step, or a forecast note. The plugin can apply it after approval. It cannot bypass a field the user cannot see. It cannot write as a hidden admin unless someone connected an admin user.

That last case is the unofficial path: a homemade MCP server, a pasted password, or a shared integration login in chat history. The official plugin is built to avoid that. Unofficial setups still do it.

What Salesforce already governs

Give the plugin credit.

• Object, field, and record access follow the authenticated user.
• Sharing rules still apply. If the seller cannot see the account, Claude cannot either.
• Tool calls show up in Event Monitoring.
• The default write path asks before it changes the CRM.

If the question is "is Salesforce in Claude a random public chatbot with your pipeline," the answer is no.

What a chat still cannot govern

RevOps does not get paid for one approved write. It gets paid for the same write, on the same kind of deal, when nobody is watching.

A plugin skill is instructions in a conversation. A playbook is a saved process.

Need	Salesforce in Claude	Saved playbook
Who can see the record	Yes, the signed-in user	Yes, a scoped integration user
Who can change the process	Anyone in the thread can talk it into a different policy	Owners and editors only
Same stage rule every Tuesday	Chat re-decides	Same steps, same checks
Password in history	Official plugin uses OAuth. Unofficial MCP often pastes a secret	Workspace secrets, never the chat
Mid-run approval	Ask-before-write on that turn	Pause on the same run ID, then continue
Version of the rule	Prompt and skill text	Saved playbook version

A rep can still say "move this deal forward" when there is no next step. Salesforce validation may catch a required field. It will not catch a fuzzy cutoff that the chat invented this morning.

That is the gap: permissions on the user are not the same as a versioned process.

For the longer split between writing a process and running one, see Claude writes the playbook. Ballet runs it.. For personal desktop sessions vs team playbooks, see Ballet vs Claude Cowork.

How to try the beta without handing over the CRM

1. Connect Salesforce in Claude as an admin. Restrict it to a permission set, not the whole org.
2. Start read-only. Pipeline review and account research first. Writes later.
3. Use mcp_api only. Do not add the full api scope because a setup wizard failed once.
4. Do not connect a system admin as the demo user.
5. Keep unofficial MCP servers out of seller machines until they use the same least-privilege rules.
6. Log every write: who asked, which record, which fields, whether a human approved.
7. Put stage changes, owner changes, and anything a customer can see behind a saved rule, not only a chat approval.

Connecting Salesforce as a first-party integration (not a chat plugin) is documented in How do I connect Salesforce?.

Where Ballet fits

Claude is the right place to draft the skill and the rule. It is a poor place to keep the only copy of the rule.

Ballet is the run layer next to Claude:

• Ask Ballet writes a playbook from the same English a seller would type in Claude.
• The playbook runs as compiled steps: same checks, same owner assignment, same next-step requirement.
• Owners edit. Everyone else runs. The chat cannot rewrite the cutoff.
• Salesforce credentials stay in the workspace. See the connect guide above.
• A write that needs a human parks on the same run, then continues. It is not a second chat that forgot the first attempt.

On a 54-case operations bench, a compiled playbook matched its own answer 54 of 54 times. Claude matched 42 of 54. Full tables: Deterministic operations, measured.

Use Salesforce in Claude to read the pipeline and draft the update. Use a playbook when the write has to be the same tomorrow.

FAQ

What is Claudeforce? The Salesforce and Anthropic partnership announced 27 August 2026. Salesforce in Claude is the first product.

Is Salesforce in Claude generally available? No. Open beta started 15 September 2026 on paid Claude plans. An org admin has to connect it. A solo Pro user cannot flip it on without Salesforce admin access.

Can Claude update Salesforce without the plugin? Yes, through unofficial MCP or a custom integration. That is how passwords land in chat history. Prefer the hosted plugin or a workspace connector with a scoped user.

Do you still need the Salesforce app? For reporting, admin, and most sellers' day-to-day, yes. The plugin covers research, pipeline review, and drafted updates. It does not replace Setup, permission sets, or forecast meetings.

Is Salesforce in Claude safe? Safer than a pasted password. Not the same as a versioned process. Safety here means the user's existing Salesforce permissions plus ask-before-write. It does not mean every Tuesday's stage change will match Monday's policy.

Should RevOps block the plugin? No. Block shared admin logins and unofficial MCP. Allow read-only pilots. Move stage changes and routing onto a saved playbook.

Related articles

• Claude writes the playbook. Ballet runs it.
• Ballet vs Claude Cowork
• How do I connect Salesforce?
• Deterministic operations, measured
• RevOps recipes
• Why Ballet

Sources

• Salesforce, Claudeforce announcement (27 August 2026)
• Salesforce, Expanding Headless 360
• Salesforce Developers, How to Secure Salesforce Hosted MCP Servers (June 2026)
• VentureBeat, Salesforce just put its entire CRM inside Claude
• Coursiv, Salesforce in Claude beta (15 September 2026)