Is your Salesforce org safe for Agentforce and MeshMesh?

Read the sources on Nov 11, 2026. Run the checklist yourself, or have Wrenk do the cleanup.

Agents inherit whatever your org already allows: the permissions, the sharing rules, the automations and the integration users. Before an agent such as Agentforce or MeshMesh gets write access, clean up what it can reach and know which copy you would restore from. The checklist below is one an admin can run alone, with no Wrenk involvement.

Why now

  • Salesforce is auto-enabling Agentforce in Winter '27 for orgs with Agentforce access, which Salesforce Ben lists as Foundations on Enterprise, Performance, Unlimited and Developer Edition, plus Agentforce 1 Edition. Its article is dated 2026-08-31 and says the change was in preview, with no additional cost stated by Salesforce. Salesforce Ben
  • The MeshMesh beta opened on 2026-11-05, and on 2026-11-09 its docs added an "Audit Snapshot of Org Health" recipe, described as a read-only health check. It is a beta, not generally available. docs.meshmesh.io
  • SaaStr wrote that a well-regarded agent from a vendor it chose not to name deleted nearly all of its Salesforce opportunities shortly after being connected, and that the vendor's agent had no rollback. It restored from a snapshot it had never planned as a backup. Its new rule: "A new vendor's agent starts read-only on our systems." SaaStr

What to check before an agent gets write access

Six checks an admin can run in Setup with no outside help. They apply to any agent, from any vendor.

  1. Who holds Manage AI Agents. Salesforce Ben notes that non-admin users need the Manage AI Agents permission to build agents. List every user and permission set that has it, and remove it from anyone who does not need it.
  2. Org-wide defaults and over-broad sharing. Review org-wide defaults on the objects an agent will touch, and any sharing rules, profiles or permission sets that grant View All, Modify All or broad delete. An agent can reach whatever its user can reach.
  3. Which user the agent runs as, and what that user can modify or delete. Find the user or integration identity the agent acts as. Open its effective permissions on each object and field. If that user can delete opportunities, so can the agent. Prefer a dedicated user with the narrowest access that works.
  4. Automations that fire on the objects the agent will touch. List the flows, Apex triggers, validation rules and process automation on those objects. An agent's single write can start a chain of other writes, emails or callouts. Know the chain before the agent starts it.
  5. Integration users and what writes overnight. Inventory integration users, connected apps and scheduled jobs that write to the same objects. Overlapping writers are how an agent's change gets overwritten, or how it overwrites someone else's.
  6. What you would roll back, and from which copy. For each object an agent can write, name the independent copy you would restore from and when it was last taken. Check that the agent cannot write to that copy. If you cannot name it, the agent should start read-only.

Two agent systems in one org

When MeshMesh, Agentforce or Wrenk can all change the org, four questions need one named answer each:

  • Who may write? Name each agent system and the user it runs as, and what each may create, change or delete.
  • Which sandbox? Decide where each agent's changes are tested first, and whether two systems can touch the same sandbox.
  • Who approves production? One named person or group signs off on production changes, whichever system proposed them.
  • Who owns rollback? One owner, with the copy to restore from, for changes made by any of the systems.

See also Salesforce MeshMesh, explained and Claudeforce readiness.

Where Wrenk fits

The audit is now a commodity. MeshMesh and several other tools will run one, and you can run the checklist above yourself. Wrenk is the independent team that does the cleanup and stays on. It is an AI admin team and platform: agents plan and make the fixes with your approval, and people stand behind them. It works across Salesforce and HubSpot, is built to support ServiceNow, and works inside Claude, ChatGPT, Gemini and Copilot.

Prices read from wrenk.ai/pricing on Nov 11, 2026.

  1. Free health check: free, three questions, no account, nothing connected.
  2. Org Repair: $1,500 one-time. A Wrenk admin works through your findings.
  3. Monitoring Membership: $300 per month. Scheduled checks, with a Wrenk admin handling what comes up.
  4. Managed Operations: from $3,000 per month. Wrenk works your backlog for you.

FAQ

Is MeshMesh generally available?

No. As read on Nov 11, 2026, MeshMesh is a Customer Hands-On Beta. Its docs list the beta as live on November 5, 2026, with an estimated end date of January 31, 2027, and say general availability is planned for Salesforce fiscal year 2028. Pricing after the beta is still being determined.

Does Agentforce turn on by itself?

For many orgs, yes. Salesforce Ben reported on August 31, 2026 that in Winter '27 Salesforce is auto-enabling Agentforce in orgs with Agentforce access, including Enterprise, Performance, Unlimited and Developer Edition orgs with Foundations, and Agentforce 1 Edition orgs. It said the change was in preview and that Salesforce stated there is no additional cost. Admins keep controls such as the Einstein setting and activating or deactivating an agent. Check Salesforce's release notes for your org.

Do I need a readiness audit tool?

Not necessarily. The checklist on this page is one an admin can run with no tool. Audits have also become common: MeshMesh added an org-health audit recipe on 2026-11-09, and several other tools offer one. Choose a tool if it saves your admin time. The harder part is the cleanup and keeping it clean.

What does Wrenk do that a tool does not?

Wrenk is an AI admin team and platform: agents plan and make fixes with human approval, and a team behind them does the work. It is independent of Salesforce, covers HubSpot as well as Salesforce, is built to support ServiceNow, works inside Claude, ChatGPT, Gemini and Copilot, and is for sale today at published prices. A tool is something your team drives. Managed Operations is for when nobody has the time.

What does it cost?

Prices read from wrenk.ai/pricing on Nov 11, 2026: the free health check is free (three questions, no account, nothing connected). Org Repair is $1,500 one-time. Monitoring Membership is $300 per month. Managed Operations starts at $3,000 per month. Confirm current prices on the pricing page.

Sources: Salesforce Ben, Salesforce to Auto-Enable Agentforce in Winter '27 (2026-08-31), docs.meshmesh.io (llms-full.txt), SaaStr, Two AI Agents Wiped Critical Data at SaaStr and wrenk.ai/pricing. All were read on Nov 11, 2026.

Is anything here unconfirmed? Yes. The Agentforce auto-enable timing comes from a news report that called it a preview, so check Salesforce's release notes for your org. We did not test MeshMesh or Agentforce, and we describe them only from these pages. The SaaStr account is theirs, about an agent they did not name. Terms and prices move, so confirm them at the source.

Start with three questions

The free health check gives a peer-benchmarked score. No account, nothing connected.