The short version
- With Winter ’27, the Agentforce platform is enabled by default in eligible orgs: per the release notes, "the Agentforce platform is enabled by default for all orgs with Agentforce access." Rollout has been running since early September, with production waves through October 10.
- Enablement is not deployment. No agent starts talking to your customers on its own; what changes is that the platform is on and anyone with the right permission can build.
- The real exposure is governance plus credits: agent actions meter at 20 Flex Credits in production (16 in sandbox), credits do not roll over, and overage bills monthly in arrears.
- If you want it off, the reliable paths are the Einstein generative AI master switch (with an org-wide caveat), deactivating individual agents, and trimming the Manage AI Agents permission. Do not build your plan on the Setup toggle; it is being removed later in the release cycle.
- Ten minutes of admin work now, inventory, permissions, credit model, beats an invoice conversation in January.
What Actually Turned On
Somewhere between early September and October 10, your org almost certainly joined the Winter ’27 release, and with it a change that reads scarier than it is: per the release notes, "the Agentforce platform is enabled by default for all orgs with Agentforce access." In scope: Lightning Experience orgs with Foundations on Enterprise, Performance, Unlimited, and Developer editions, plus Agentforce 1. Out of scope: Professional, Essentials, and orgs without Agentforce access. Agentforce Coworker does not auto-enable, and neither does any Data Cloud entitlement.
The sentence that matters most: enablement is not deployment. No agent starts answering your customers on its own. What changed is that the platform is on, and anyone holding the Manage AI Agents permission can now build on it. That shifts the question from "is this dangerous?" to "who in our org can build, and what will it cost when they do?"
To find your exact enablement date, look up your instance on Salesforce Trust and open the Maintenance tab.
The Credit Question Everyone Asks First
Enablement itself is free: no charge, no billing change. The exposure is downstream, and it is worth having the numbers on one line: agent actions meter at 20 Flex Credits in production and 16 in sandbox, credits do not roll over, and overage bills monthly in arrears at your contracted rate. The Digital Wallet shows you consumption but does not block execution when the bundle runs out.
Two sharp edges inside that. First, sandbox consumption is real consumption, so an enthusiastic builder running simulations burns credits nobody budgeted. Second, contracts sold as "unmetered" require the Unmetered User-Based AI permission set license to actually be assigned; per the published admin guidance, users without it consume credits even on unmetered paper. If your CFO has heard the word unmetered, verify the assignment per user this week.
For what a credit is worth in dollars and how the bundles compare across the new editions, our Core vs Advanced vs Max guide has the arithmetic, and the ROI playbook turns it into a forecast.
If You Want It Off
Three levers exist, and picking the right one matters:
- The Einstein generative AI setting in Setup is the master switch, but it is org-wide: disabling it takes down Einstein AI features across the org, and Salesforce has not published a complete inventory of what that includes. Record what you depend on before you pull it.
- Individual agents can be deactivated in the builder, which is the right tool when something specific was switched on that should not have been.
- The Manage AI Agents permission controls who can build at all. Trimming it is the quietest and usually the correct control: the platform stays on, and nothing new appears without a named owner.
- Do not build your plan on the Setup Agentforce toggle. Per the release coverage, Salesforce is removing that toggle later in the Winter ’27 cycle; a disable strategy that depends on it has a shelf life.
The Ten-Minute Admin Checklist
Run this once and the auto-enablement becomes a non-event:
- Confirm your edition is in scope, and your actual enablement date on Salesforce Trust (Maintenance tab).
- Record the current state of the Einstein generative AI setting, and what else in your org depends on it.
- Inventory who holds Manage AI Agents, and trim it to people who should genuinely be building.
- Inventory existing agents: created versus activated, and which channels any active one is connected to.
- Write down the credit model: 20 per action in production, 16 in sandbox, no rollover, overage monthly in arrears.
- If your contract says unmetered, verify the Unmetered User-Based AI permission assignment per user.
- Decide, on paper, whether your org is adopting deliberately this quarter or deferring, so the next person who asks gets an answer instead of a shrug.
If the inventory turns up agents nobody owns, or you want the governance layer stood up properly before builders arrive, that is a fixed-price scope for our Agentforce practice, and a free 30-minute call sizes it. Our governance stack explainer covers the longer arc.