Claudeforce Readiness: What to Audit Before You Connect Claude to Your Salesforce Org

On August 26, 2026, Salesforce and Anthropic announced Claudeforce. Claude became the default foundation model across Agentforce surfaces, and a Salesforce plugin for Claude shipped with 37 prebuilt sales skills. Open beta is expected in September 2026.

The architecture is what matters. The Salesforce-in-Claude plugin runs on Salesforce's Headless 360 MCP server with four tools — discover, describe, dispatch and dispatch_readonly. A single administrator connection enables org-wide access that is then scoped to each individual user's permissions; every call runs as the person making it, and permission enforcement happens in your org, not in Claude. So your permission model is now your security model, and whatever it currently allows, an agent can do at machine speed.

What permissions does Claudeforce need?

One admin-level connection establishes the link. After that, each user's own permissions govern what the agent sees and does on their behalf, via per-user OAuth. There is no separate Claudeforce permission set that narrows this for you.

If a profile can export every Account, the agent can too, for that user. Over-provisioning that has been survivable for years — because a human had to click through a UI to reach it — becomes directly reachable the moment an agent can call anything that user could.

Is my Salesforce org ready for Claudeforce?

Four dimensions decide it.

1. Permission surface. Count active users with Modify All Data or View All Data across profiles and permission sets. In a 3–10 year old org this number is almost always higher than the admin expects, because permission sets accumulate and nobody removes them.
2. Automation blast radius. Agent writes are not exempt. Validation rules, flows and Apex triggers fire normally. A single bulk update issued by an agent can cascade through automation nobody has mapped since the person who built it left.
3. Documentation coverage. If no current inventory exists of what fires on your top objects, nobody can review what the agent did afterward. An agent inherits exactly the visibility you already have, which in most inherited orgs is partial.
4. Recovery readiness. Not "do we have backups" but "when did we last restore from one". An agent with broad write access and an ambiguous instruction produces a bad afternoon at a scale a human mistake does not reach.

What should I audit before connecting Claude to Salesforce?

1. Active users with Modify All Data / View All Data, counted across profiles and permission sets.
2. Connected apps and integration users holding write access, with a last-used date on each.
3. Flows, process builders and triggers firing on your top three objects — documented and current, or not.
4. Guest user and community profile permissions. This is the most commonly forgotten write path.
5. Last successful restore test, with a date.
6. Sandbox freshness — an environment mirroring production closely enough to test agent actions before production sees them.

Does Claudeforce bypass validation rules and flows?

No. Automation executes normally on agent-initiated writes. That is good news for data integrity and bad news for anyone assuming an agent operates in a quiet sandbox lane. Your existing automation is the thing that turns one agent action into fifty downstream records.

How do I limit Claudeforce to read-only?

Start with dispatch_readonly and keep it there through the pilot. Read-only lets you observe what the agent reaches for — which objects, which fields, which users' scopes — before any write path opens. Phase writes in by user cohort afterward, not by flipping the org.

How long does a Claudeforce readiness check take?

Wrenk's free health check takes about 60 seconds and needs no account and no org connection. Three questions produce a preliminary score — on data accuracy, validation rule coverage and feature adoption — benchmarked against orgs of your platform, industry and user count. Seven more optional questions, covering automation health and governance, sharpen it further.

Be clear about what that is: an estimate built from your own answers, not a measurement of your org. It is triage, telling you whether you are in the bottom quartile for agent readiness and which dimension is dragging you there. If you answer "I don't know" to most of it, that is itself the finding, because an agent inherits whatever you cannot currently see.

The measured version — actual permission counts, actual automation inventory, actual dependency mapping — requires connecting the org, which is what Wrenk's connected audit does, and what Managed operations then fixes on an ongoing basis.

Sources

• Salesforce and Anthropic announce Claudeforce — Salesforce press release, August 26, 2026.
• Claudeforce product page — Salesforce.
• Claudeforce explained: what Salesforce & Anthropic actually ship — Apex Hours.

Managed operations from $3,000/mo — we fix what the audit finds.