Overview
- Salesforce is switching Agentforce on by default for every eligible org starting with the Winter ’27 release.
- The rollout begins in the first week of September on a staggered basis, and no extra licence purchase is required.
- Admins keep full control through Setup, so agents can still be paused, reconfigured, or deactivated at any time.
- The move signals where Salesforce AI agents are headed platform-wide, from Agentforce for Sales to Agentforce for Service.
If you have been waiting for the next big piece of Agentforce news, this is it. Salesforce has confirmed that Agentforce will soon be enabled automatically in every org that already qualifies for it, removing a manual setup step that many admins never completed. It is one of the more consequential changes buried inside the latest Salesforce release notes, and it affects a huge share of the customer base overnight.
For anyone closely tracking Agentforce news, this single change says more about Salesforce’s AI direction than most product announcements this year.
Agentforce News: What's Actually Changing
According to Salesforce’s official Winter ’27 release notes on Agentforce auto-enablement, any org running Lightning Experience on Foundations (Enterprise, Performance, Unlimited, or Developer Edition) or on an Agentforce 1 Edition licence will have the Agentforce platform switched on automatically. New orgs get it from the moment they are provisioned. Existing orgs are being migrated in waves rather than all at once, which is why some teams may notice the shift before others.
Practically speaking, this means the on/off toggle that currently sits on the Agentforce Agents page inside Setup is being phased out entirely. Instead of an admin having to flip a switch before anyone can touch Agentforce Builder, the feature will simply be present and ready to use. Salesforce frames this as removing friction from the build-test-deploy cycle, letting teams go from an idea to a working agent without an extra configuration step standing in the way.
This is still rolling out in preview, so it won’t count as generally available until Salesforce confirms a firm GA date — enabling the Agentforce platform for the underlying setup mechanics.
Does This Change What You Pay?
This is usually the first question that comes up whenever Salesforce Agentforce expands into more orgs, and the answer here is straightforward: Salesforce says auto-enablement carries no additional cost and will not alter existing billing arrangements. Turning the platform on does not, by itself, put a company on the hook for new consumption charges.
That said, teams that have been paying attention to Salesforce Agentforce pricing know that usage-based costs kick in once agents actually start doing work — resolving cases, qualifying leads, or completing actions that draw on Agentforce credits. Simply having the platform switched on is not the same as running agents that consume credits.
Finance and ops teams should treat this as a visibility change rather than a budget change, worth a quick check against your consumption dashboards. See how TechForce Services supports Agentforce deployments if you’re weighing this up for your org.
Why Roll This Out Now?
This is where the Agentforce news gets more interesting than a routine setup tweak. Salesforce’s stated reasoning is fairly simple: making Agentforce available by default should make it feel like a natural part of the platform rather than an optional add-on that has to be discovered and switched on.
This mirrors Salesforce’s notes on the Agentforce Coworker rollout from earlier this year. Whether it actually changes adoption is the more interesting question. Agentforce revenue keeps climbing quarter over quarter, but revenue growth and active usage aren’t the same metric — that gap only closes once orgs get to how autonomous agents complete full work units, not just switch the platform on.
This also lines up with a broader pattern of investment. Salesforce AI agents have been expanding well beyond the original assistant concept, showing up across the entire product line under the Agentforce 360 umbrella.
Agentforce for Sales now helps reps prioritize pipeline and draft outreach, while Agentforce for Service handles case triage, knowledge lookups, and routine replies — see how Agentforce is reshaping service teams for a sense of how far this has moved beyond simple chatbots. Auto-enabling the underlying platform is arguably a precondition for all of these surfaces to see real traction, since none of them work if the base capability sits dormant behind a Setup toggle nobody flipped.
A year ago, Salesforce Agentforce AI features were largely opt-in add-ons requiring a dedicated evaluation project. Today, the platform assumes most customers will want some form of agent running somewhere in their org, and it’s building the default experience around that assumption — turning agent building from a special initiative into a standard platform capability.
What Admins Need to Do
For most organizations, no immediate action is required. If Einstein generative AI is already active in your org, admins will have direct access to Agentforce Builder as soon as the change lands. To extend that access to non-admin users, assign the Manage AI Agents permission to the relevant profiles or permission sets — this is the same control that existed before, and it isn’t going away.
Salesforce is keeping several guardrails in place even after the toggle disappears:
- The Einstein setting on the Einstein Setup page can still be switched off to disable the Agentforce platform entirely for an org.
- Individual agents can be activated or deactivated inside Agentforce Builder without touching the platform-level setting.
- Permission sets still gate who can build, edit, or publish an agent, so access isn’t handed to every user by default.
Worth a look too: the governance and monitoring tools built into the latest release, since visibility matters more once agents run by default.
It’s a sensible moment for admins to audit existing permission sets, confirm which profiles currently hold Manage AI Agents, and flag the change to any team that hasn’t started experimenting with agent building yet. Documenting who has access now also makes it much easier to answer questions later, whether that’s from security, procurement, or a curious executive who just read the same Agentforce news you did.
What This Means for the Bigger Picture
For anyone following Agentforce news beyond this single release, auto-enablement is a small technical change with an outsized signal attached to it. Salesforce is betting that removing a single click from the setup flow will nudge more teams toward building their first agent, and that familiarity — not just capability — is what has been holding adoption back in cautious orgs. The admin-level controls staying intact suggests Salesforce knows plenty of customers still want to move at their own pace, especially in regulated industries or teams new to Salesforce AI agents generally.
FAQ
Will Agentforce turn on automatically in my org?
Yes, if your org has Foundations on Enterprise, Performance, Unlimited, or Developer Edition, or an Agentforce 1 Edition licence, it will be enabled as part of the rolling Winter ’27 update.
Does auto-enabling Agentforce cost extra?
No. Salesforce has confirmed there is no additional charge and no change to billing simply for having the platform switched on.
Can I still turn Agentforce off if I don't want it active?
Yes. Admins can disable the Einstein setting on the Einstein Setup page, or deactivate individual agents inside Agentforce Builder, at any time.
What's the biggest piece of Agentforce news in this release?
The removal of the manual Setup toggle — Agentforce access now ships on by default for every eligible org, rather than waiting for an admin to switch it on.
