If you’re a Salesforce customer with Foundations or an Agentforce 1 Edition licence in your org, a change is coming by the end of this month that you may not even know about.
In Winter ‘27, Salesforce is auto-enabling Agentforce by default in all orgs with Agentforce access. This comes after Agentforce Coworker started becoming automatically available for some customers on a rolling basis earlier this month. Salesforce maintains that this comes at no additional cost and that there will be no changes to billing; here’s everything you need to know.
What’s Happening?
As part of the Winter ‘27 release, Salesforce will be auto-enabling Agentforce for all orgs with Agentforce access, as granted by SKUs, licensing, and editions. Salesforce says that new orgs are enabled at creation, and existing orgs will be auto-enabled. This affects orgs on Lightning Experience with Foundations on Enterprise, Performance, Unlimited, and Developer Edition as well as those on Agentforce 1 Edition.
This means that the Agentforce toggle will be removed from the Agentforce Agents page in Setup, enabling users to “build, test, and deploy agents with one less step.” At this time, Salesforce stresses that this release is currently in preview and that this change doesn’t become generally available until the latest general availability date that Salesforce announces for this release.
Originally, Salesforce had planned to roll this out in August, but the company now plans to begin enabling the Agentforce platform for existing orgs on a rolling basis starting the first week of September. After that, removing the Agentforce setting is planned for later in Winter ʼ27.
Will This Cost Me More?
Salesforce specifically maintains that enablement of Agentforce by default will not incur any additional cost, and that it will not make changes to billing.
It is not yet clear as to whether further information on this will be provided, as Salesforce did for the auto-enablement of Agentforce Coworker, but the release notes Help page indicates that more details will come at a later date.
SF Ben has reached out to Salesforce for comment.
Why Now?
Salesforce claims that this change is intended to make working with and building with Agentforce feel more natural. However, it is currently unclear whether or not this will impact Agentforce’s adoption metrics.
Agentforce revenue continues to rise, indicating a growing number of deals. But when it comes to adoption, will this change mean the number of “active” Agentforce users increases?
What To Do Next
At this stage, no real steps need to be taken if you have an org that will be impacted by this change. If Einstein generative AI is enabled in your org, admins will have immediate access to Agentforce Builder. To give other non-admin users access to build agents, assign the Manage AI Agents permission.
Salesforce will continue to offer certain controls to manage access to Agentforce, including turning off the Einstein setting on the Einstein Setup page to turn off the Agentforce platform, and the ability to activate or deactivate an agent in Agentforce Builder.
Final Thoughts
Ultimately, this change represents Salesforce’s commitment to simplifying the setup process, allowing teams to move from configuration to deployment with greater speed and fewer technical hurdles. While the auto-enablement might seem like a significant shift, the preservation of admin controls ensures that organizations can still manage their AI journey at their own pace.
It will be interesting to observe how this small reduction in friction influences long-term adoption and whether it encourages more hesitant teams to finally explore the full potential of the Agentforce platform.
