ANALYSIS · SALESFORCE + AI
Winter '27 turns the Agentforce platform on for orgs that already have access. It does not create an agent, and the Setup toggle Salesforce is removing is not the remaining off-switch.
By Enterprise Dreamin Editorial Team
Salesforce is auto-enabling the Agentforce platform in Winter '27 at no additional cost for orgs that already have access, without creating or activating any agent; Flex Credits still meter Standard and Custom Actions at 20 credits in production and 16 in sandbox with no rollover; and the remaining org-level off-switch is Einstein generative AI, which takes other Einstein gen AI features with it.
That sentence is the operational picture. What follows is the remaining controls, who is in scope, and the checklist before the Winter '27 production weekends.
Sasha Semjonova at Salesforce Ben reported the Winter '27 release-note change on 31 August 2026. Salesforce Ben amplified it on X on 1 September 2026 at 11:00 AM CT. Dipojjal Chakrabarti is Founder and Editor of Salesforce Dictionary, a B2C Solution Architect with 29 Salesforce certifications and 13-plus years on the platform. He published the enablement-versus-metering cut on 2 September 2026. Semjonova is cited here as the journalist who reported the notes and the unanswered billing follow-up. Chakrabarti is cited for enablement versus metering. Neither recap is the disable path.
Does auto-enable turn an agent on?
No. Auto-enable turns the Agentforce platform on. It does not turn an agent on.
Releasebot extracted Salesforce's Winter '27 "Agentforce and Generative AI Release Notes" (first seen 18 August 2026, updated 29 August 2026). Live Help child pages are JavaScript shells; the verbatim paragraph below is from that extract, not from a rendered Help page. Salesforce's Winter '27 release notes hub is the official parent.
In Winter '27, the Agentforce platform is enabled by default for all orgs with Agentforce access, as granted by SKUs, licensing, and editions. New orgs are enabled at creation, and existing orgs will be auto-enabled. The Agentforce setting will be removed from the Agentforce Agents page in Setup, so you can build, test, and deploy agents with one less step. The platform is enabled at no additional cost and there are no changes to billing.
Platform on is not agent on. Salesforce's Agentforce DX documentation separates those steps. Quote: "Activating an agent makes it available to users on the channels that your agent is connected to." Create and activate remain separate steps. Auto-enable does not publish an agent to a channel. It does not mean a bot is answering cases.
The notes are still in preview. Features described do not become generally available until the latest general availability date Salesforce announces for the release. Semjonova reported that caveat on 31 August.
Salesforce originally planned to enable existing orgs in August. Rolling enablement instead started the first week of September 2026. Semjonova reported that slip. Chakrabarti described the rollout as happening now as of 2 September. Removal of the Setup toggle is later in Winter '27, not day one of rolling enablement.
What is the remaining org kill switch after the Setup toggle goes away?
Einstein generative AI. Salesforce's org-setup documentation says: "To access Einstein generative AI features in your org, you must turn on Einstein." The path is Setup > Einstein Setup.
Semjonova reported that Salesforce will continue to offer controls. One is "turning off the Einstein setting on the Einstein Setup page to turn off the Agentforce platform." Activate or deactivate in Agentforce Builder remains available. Chakrabarti called Einstein the remaining org-level off switch once the Agentforce toggle is gone, and a blunt one: it takes other Einstein features down with it.
That blast radius is the tradeoff. Salesforce has not published an inventory of which Einstein generative AI features die when that setting is off. Breadth is Ben and Dictionary analysis, not a Salesforce list. Turning Einstein generative AI off to kill Agentforce is an org-wide generative-AI decision, not an Agentforce-only switch.
Until toggle removal later in Winter '27, the Agentforce Agents Setup control may still exist and already be switched on. A live AI overview that still says "go to Setup > Agentforce Agents and toggle off" is describing the control Salesforce is removing.
Is Manage AI Agents the real boundary after the platform is on?
For building, yes. Salesforce Help for creating an HR service agent from a template requires Manage AI Agents, alongside agent-type permissions or Customize Application.
Semjonova's 31 August report: if Einstein generative AI is already enabled, admins get immediate access to Agentforce Builder. Non-admin users need Manage AI Agents assigned.
Manage AI Agents is not an off-switch for a live agent. Activation remains a separate act in Agentforce Builder. Deactivation remains the control for an agent that already exists. Auto-enable does not grant Builder access to every user.
The practical boundary after the platform is on is permission, plus activation, plus channel connection. Not the Setup platform toggle Salesforce is removing.
| Control | After auto-enable | What it does not do | Source |
|---|---|---|---|
| Agentforce setting on Agentforce Agents (Setup) | May still exist early in Winter '27, already on | Remain as a durable off-switch. Salesforce removes it later in Winter '27. | Release notes via Releasebot; Semjonova; Chakrabarti |
| Einstein generative AI (Setup > Einstein Setup) | Remaining org-level off-switch for the Agentforce platform | Agentforce-only. Takes other Einstein generative AI features with it. Salesforce has not published that inventory. | Salesforce org-setup docs; Semjonova; Chakrabarti |
| Manage AI Agents | Who can build in Agentforce Builder | Activate, deactivate, or publish an agent | Salesforce Help; Semjonova |
| Activate / deactivate in Agentforce Builder | Makes an agent available on connected channels, or takes it off those channels | Create the agent. Turn the platform off. | Agentforce DX |
| Coworker Turn On | Coworker's own enablement | Follow from platform auto-enable. Still requires Data Cloud or Data 360. | Coworker infrastructure docs |
Is enablement free? What about metering and "unmetered"?
Enablement is free. Metering is not.
Chakrabarti, analysing Salesforce's commercial claim rather than quoting a Salesforce sentence:
Enabling a capability and metering a capability are separate events, and only the first one is free.
— Dipojjal Chakrabarti, Salesforce Dictionary, 2 September 2026
The 18 August 2026 Flex Credits Rate Card prices Standard Actions and Custom Actions at 20 Flex Credits in production and 16 in sandbox. Unused Flex Credits do not roll over.
Salesforce's Agentforce pricing FAQ bills usage past entitlement at the contracted rate, monthly in arrears. Digital Wallet does not block execution at the credit cap.
"Unmetered" is SKU-scoped, plus the Unmetered User-Based AI permission set license. Salesforce's Coworker infrastructure documentation is direct. Without that assignment, "users still consume credits." A Salesforce Help FAQ (005197697, published 27 September 2025) places Flex Credits "outside the scope of unmetered employee AI usage" and states you will still need Data Cloud and Data Services Credits to support AI usage.
Foundations is listed at $0 on the Agentforce pricing page. Agentforce 1 Editions start at $550 per user per month, with 2.5 million Flex Credits per org per year.
Semjonova reported on 31 August that more billing detail "will come at a later date," and that Salesforce Ben had reached out to Salesforce for comment. No Salesforce reply is published in that piece as of 3 September 2026.
Practitioner threads are already mixing "unmetered" with "no bill." A 2 September 2026 r/salesforce thread asked whether AI described as unmetered still has cost. Replies distinguished internally triggered actions from sub-agents, and SKU-scoped unmetered from unmetered full stop. An account executive on the thread deferred to Dreamforce. Those comments are practitioner confusion, not Salesforce documentation. The live thread returned HTTP 403 on 3 September 2026 and was not re-verified on-page. Do not treat any "2-3x" inflation figure from that thread as fact. Official docs already support SKU-plus-assignment unmetered, which is the part that is checkable.
| Item | Figure | What it covers | What it does not cover | Source |
|---|---|---|---|---|
| Platform auto-enable | No additional cost; no billing changes | Platform availability for in-scope orgs | Flex Credit consumption, Data 360 credits, overage | RN via Releasebot |
| Standard / Custom Action | 20 prod / 16 sandbox Flex Credits | Each Standard or Custom Action | Rollover | Flex Credits Rate Card, 18 Aug 2026 |
| Foundations | $0 | The Foundations SKU on the pricing page | A billing holiday once agents run | Agentforce pricing |
| Agentforce 1 Editions | From $550/user/month; 2.5M Flex Credits per org per year | Seat edition plus included Flex Credits | Unmetered full stop; Data Cloud / Data 360 credits | Agentforce pricing |
| Unmetered User-Based AI PSL | Assignment required on qualifying SKUs | Seat-based unmetered path | Users without the PSL; Data Cloud / Data Services Credits | Coworker docs; Help FAQ 005197697 |
| Overage | Contracted rate, billed monthly in arrears | Usage past entitlement | A hard stop in Digital Wallet | Agentforce pricing FAQ |
Who is in scope for Winter '27 auto-enable?
Not every org.
Semjonova, attributing Salesforce: Lightning Experience with Foundations on Enterprise, Performance, Unlimited, and Developer Edition, plus Agentforce 1 Edition. The release notes phrase is "as granted by SKUs, licensing, and editions."
If the org does not already have Agentforce access, this auto-enable does not apply. Do not infer Professional or Essentials coverage from the Foundations $0 sticker. The in-scope list above is the list Semjonova attributed to Salesforce.
Does platform on mean Coworker is on?
No. Platform auto-enable does not turn Agentforce Coworker on.
Coworker still requires Data Cloud or Data 360, and its own Setup Turn On. Salesforce's Coworker infrastructure documentation blocks activation until pre-enablement is complete. Salesforce Help describes Coworker as powered by Data 360. Connecting Data 360 sources to Coworker consumes Data 360 processing and query credits.
A provisioned Data 360 SKU is not the same as an implemented Data 360 program. Platform auto-enable does not close that gap. Orgs can have the Agentforce platform on and still be unable to turn Coworker on.
What should admins check before the Winter '27 production weekends?
Ella Marks of Salesforce Admin Relations, writing on 6 August 2026, listed the Winter '27 production weekends as 4 September, 2 October, and 9 October 2026. 4 September 2026 is the first production upgrade weekend. That date is not proven as the Agentforce auto-enable date for a given org. Auto-enable is rolling in the first week of September and can precede, or not equal, the instance upgrade.
- Confirm SKU and edition against the in-scope list. If the org is not on Lightning Experience with Foundations on Enterprise, Performance, Unlimited, or Developer, and is not Agentforce 1 Edition, stop. This release note is not that org's change.
- Record the current state of Einstein generative AI at Setup > Einstein Setup. If it is on, admins with access get Agentforce Builder when the platform is on. If the plan is to turn it off, treat that as an org-wide generative-AI decision. Salesforce has not published what else dies.
- Inventory who has Manage AI Agents. That permission is the build boundary after the platform is on, not an activation control.
- Inventory existing agents: created versus activated, and which channels each is connected to. Auto-enable does not activate them. Someone with Builder access still can.
- Do not treat Coworker as in the auto-enable bundle. Confirm Data Cloud or Data 360 entitlement separately from whether a Data 360 program is actually implemented.
- Model Flex Credits at 20 per Standard or Custom Action in production, 16 in sandbox, with no rollover. Digital Wallet will not stop execution at the cap. Overage bills monthly in arrears.
- If the org was sold "unmetered," confirm both the SKU and the Unmetered User-Based AI assignment. Without the permission set license, users still consume credits. Data Cloud / Data 360 credits still apply.
- Do not wait for the Agentforce Agents Setup toggle to remain as a quiet off-switch. Semjonova and Chakrabarti both place its removal later in Winter '27, not on day one.
Winter '27 also changes the default model path. That is a separate article: what changes with Claude as the Salesforce default model. Dates overlap. The control being removed here is the Agentforce platform setting, not the model picker.
Why do AI overviews still tell you to flip a toggle Salesforce is removing?
Because the disable query is still served by pre-Winter '27 how-tos.
As of 3 September 2026, live AI overviews for "disable Agentforce Salesforce" still tell admins to use Setup > Agentforce Agents, the control the Winter '27 notes remove. Overviews for "Einstein generative AI disable Agentforce" currently say there is no single global toggle, which conflicts with Semjonova and Chakrabarti on Einstein Setup.
Salesforce Help's Winter '27 hub exists. Live child pages are JavaScript shells. The verbatim platform-auto-enable paragraph in this piece is quoted from Releasebot's extract of Salesforce's Agentforce and Generative AI release notes.
Semjonova reported the notes and the unanswered billing follow-up. That is the news story. The remaining work for an admin is the disable path above. Related controls sit in AI governance for Salesforce, securing AI in Salesforce, and Agentforce pricing explained.
When this answer does not apply
It does not apply to orgs without Agentforce access via SKU, license, or edition. It does not apply as a Coworker-on event. It does not apply as a billing holiday. It does not apply as a proven 4 September auto-enable for every instance.
It also does not apply as a reason to leave Einstein generative AI on, or off, for tools that are not Agentforce. Admins running a non-Agentforce Salesforce AI path still have to decide Einstein generative AI on its own blast radius, not as a proxy for this release note. Paths that do not depend on Data Cloud are covered separately in AI for Salesforce without Data Cloud.
What this means for your org
- Treat Winter '27 auto-enable as a platform-state change. Audit who can build and which agents are already activated.
- Do not use Einstein generative AI as a quiet Agentforce-only kill switch. Salesforce has not listed what else you turn off.
- Budget Flex Credits and Data 360 credits as if enablement did not happen. "No additional cost" in the notes is enablement.
- If someone said "unmetered," ask which SKU and whether Unmetered User-Based AI is assigned. Then ask what Data 360 still meters.
- Use Ella Marks's weekends (4 September, 2 October, 9 October 2026) for instance upgrade planning. Do not use 4 September as a proven auto-enable date for your org.
Methodology
Primary claims are taken from Salesforce release notes as extracted by Releasebot (Help child pages rendered as JavaScript shells on 3 September 2026), Salesforce developer and Help documentation, the 18 August 2026 Flex Credits Rate Card, and Salesforce's Agentforce pricing page. Sasha Semjonova (Salesforce Ben, 31 August 2026) is cited as the journalist who reported the notes and the unanswered billing follow-up. Dipojjal Chakrabarti (Founder and Editor, Salesforce Dictionary; B2C Solution Architect; 29 Salesforce certifications; 13-plus years) is cited for enablement versus metering. Ella Marks (Salesforce Admin Relations, 6 August 2026) is cited for production weekends. Practitioner Reddit comments are labeled as confusion, not Salesforce fact; the live thread returned HTTP 403 on 3 September 2026 and was not re-verified on-page.
YouTube, TechJack, and TechTimes were not used.
