Platform
Dreamforce 2026 for admins: Builder Central, Quick Pages, and the October pile-up
Strip the keynote down to what changes in Setup and the admin's October gets crowded: Builder Central in beta the week of September 21, Quick Pages in beta in October, Coworker AI Skills and Agent Optimizer going GA the same month, a new Security Center, a compliance agent in Privacy Center, and the Winter '27 production weekends in the middle of all of it. This is the list, with the availability Salesforce has published and the gaps where it has not.
If you administer a Salesforce org, most of Dreamforce 2026 was about other people. AIforce is for the people who never open Lightning. Koa is for the people who choose models. The named agents are for the people who buy them.
What lands on your desk is smaller and more specific: a handful of new tools in Setup, several with an October date, and a Winter ‘27 upgrade weekend sitting in the same month.
Salesforce Ben’s admin roundup by Christine Marshall is the best single list, and Salesforce’s own admin highlights cover the same ground. This post puts them in the order I would deal with them, and marks what Salesforce has and has not said about when.
Builder Central is free, and it arrives this week
Builder Central is the one to look at first, because it is the closest to shipping. Salesforce says the beta launches the week of September 21, 2026, and that it is included free in every org, gated by a permission set. I wrote up what Builder Central is and where it stops the day it was announced, so only the essentials here.
At beta it lets you create apps and agents, visualise metadata, and deploy to a sandbox with one click. Schema views, flows and permission sets are editable from the same place. More building and deployment capability is promised on the way to general availability, including the functionality that lives today in Setup with Agentforce.
The thing to decide before you assign the permission set is who gets it. A tool that builds agents and deploys to a sandbox with one click is a tool that changes metadata, and “free in every org” means the only gate is the one you set. Treat the permission set the way you treat Modify All Data, and start with the people who already have that.
Quick Pages is October, in beta
Quick Pages lets a user build reports, pages and similar artefacts by describing them. Salesforce says beta in October 2026.
There is no published detail yet on which page types, what governs who can publish one, or whether a Quick Page is metadata you can deploy or a per-user artefact. I would not plan around it until the beta notes answer those, and I would plan for the support tickets when users discover they can make pages.
Coworker, AI Skills and Agent Optimizer share a month
Three things around agents change for admins in October, and they are related.
Agentforce Coworker is available to all customers now, per the keynote, and Salesforce’s admin coverage says an admin can set it up in under five minutes. The five minutes are true. The permission-set decision that determines whether it burns credits is not in the five minutes, and it is the part to read before you turn it on.
AI Skills for Coworker, which let an employee teach the agent a task once so it can be reused, are in pilot now with general availability in October, per Salesforce’s September 11 announcement.
I covered who teaches a skill and who governs it already. From an admin’s chair the question is the same one Builder Central raises: a user can now create something the org runs. Decide the approval path before the feature arrives, not after.
Agent Optimizer, the tool that reads session traces and proposes configuration fixes, also goes GA in October. It needs session tracing enabled and landing in Data 360, and the Trust Layer’s audit collection switched on, before it can read anything. Both switches are yours, and the traces it will analyse in October have to be collected in September.
The security and privacy items
Four items on the admin list sit under security and privacy, and for all four the availability is the honest gap in the coverage: Salesforce Ben lists them without dates, and I could not find a published date either.
Security Center Essentials is a centralised security health dashboard covering the org’s security posture, managed and unmanaged packages, and trusted IP ranges. If you run the security health check by hand today, this is the product version of the same list.
Privacy Center gains a Compliance Agent that runs against the org, identifies risks and suggests fixes, and DSAR policies that enforce how a data subject access request is handled. For anyone who has assembled a DSAR response from reports, that second one is the practical item.
Transaction Security Policy accelerators, from Salesforce Labs, deploy commonly requested policies in one click, with identifying high-risk data in reports as the example. Labs packages come with the usual Labs caveat: useful, unsupported, read the code.
Winter ‘27 already moved Transaction Security Policy editing behind a dedicated permission and enforced profile filtering, both covered in the Winter ‘27 post. The Dreamforce items build on the same tightening, so the sequence is to get through the release update work first and layer the new tools on top.
Headless connections are now something you administer
The keynote’s AIforce message, that Salesforce comes to the user in Claude, Slack or Teams rather than the user coming to Salesforce, has an admin consequence that got less airtime. Those connections are MCP connections, and Salesforce says several ship out of the box with more in beta, to Slack, Microsoft Teams, Claude and ChatGPT.
Each one is an authenticated path into your org that runs as the user who connected it. The Headless 360 MCP server uses per-user OAuth against an External Client App, so the permission model is your existing one.
Reassuring, and also the point: an over-broad profile that nobody exercised in Lightning will now be exercised by a model in Claude. Before you enable any of these connections, review the user permissions of the people who will use them, and decide whether the connection is opt-in per user or on for everyone.
The October calendar
Put the dates on one page and the shape of the problem is clear.
Production orgs on the second and third Winter ‘27 waves upgrade on October 2 and October 9. Builder Central beta is live from the week of September 21 and will be in use by then. Quick Pages beta, AI Skills GA and Agent Optimizer GA all land in October. Commerce Cloud’s Google checkout goes GA in October too, if you administer a storefront.
That is a release upgrade with its own test list plus four new tools in the same four weeks.
My suggestion is to sequence rather than absorb. Winter ‘27 first, because it can break integrations. Builder Central second, because it is free and already here, and the permission set is the only decision. Coworker and AI Skills third, once you have decided who may create a skill. Quick Pages and the security tools when their beta notes give you enough to plan with.
Understanding the basics
What did Dreamforce 2026 announce for Salesforce admins?
Builder Central, free in every org and in beta from the week of September 21, 2026. Quick Pages, in beta in October. Agentforce Coworker available to all, with AI Skills going GA in October. Agent Optimizer, GA in October. Security Center Essentials, a Privacy Center Compliance Agent, DSAR policies and Transaction Security Policy accelerators, all without published dates. And out-of-the-box MCP connections to Slack, Teams, Claude and ChatGPT.
Is Builder Central free?
Yes. Salesforce says Builder Central is included in every org at no charge, gated by a permission set, with usage limits it describes as reasonable. The beta starts the week of September 21, 2026.
What is Quick Pages in Salesforce?
A feature that lets users build reports, pages and similar artefacts by describing them in natural language. Salesforce has said it enters beta in October 2026. Details on page types, governance and deployability had not been published as of September 20.
Does Agentforce Coworker cost credits?
It can. Coworker is available to all customers, but whether it consumes Agentforce credits depends on a permission-set decision the admin makes at setup. Read the enablement carefully before turning it on for everyone.
One decision covers most of the list
Builder Central, AI Skills, Quick Pages and the headless connections have one thing in common. Each lets someone who is not an admin create something the org runs or expose something the org holds, and each is gated by a permission you assign.
Decide that permission policy once, this month, and most of the October list becomes a series of the same decision. Leave it until each tool arrives and you make it four times, under time pressure, during an upgrade weekend.
If you want the October sequence planned against your own org, with the permission model reviewed before Builder Central and the headless connections go live, talk to us, or run the org health scorecard first.
