Set Up Builder Central (Beta)
Turn on Builder Central and give each admin and builder access, so your team can start building apps and agents by describing what they want.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Foundations or Agentforce 1 |
| User Permissions Needed | |
|---|---|
| To turn on Builder Central | Customize Application |
| To build apps in Builder Central | Access Builder Central |
| To assign the Access Builder Central permission to others | Assign Permission Sets, or Manage Users |
Before you turn on Builder Central, confirm that your org has Agentforce, through Foundations or Agentforce 1. Turning on Agentforce takes two distinct steps that are easy to confuse. Turn on Einstein first, and then turn on Agentforce on the Agentforce Agents page in Setup. They're separate settings. Without Agentforce, Builder Central won't load even when the beta setting is turned on.
In Einstein Setup, confirm that the Amazon Bedrock Models (Amazon and Anthropic) setting is enabled. Builder Central's Build Agent uses Anthropic models, made available through Amazon Bedrock. Because you don't select the model in Builder Central or in Setup, review this if your org restricts specific model providers. Until Amazon Bedrock is enabled, the Build Agent can't respond. Also confirm that Einstein is turned on for your org. From Setup, in the Quick Find box, enter Einstein Setup, and then select Einstein Setup. For details, see Set up Einstein AI. Until Einstein is turned on, the Access Builder Central user permission doesn't appear, so you can't assign it to your builders.
- From Setup, in the Quick Find box, enter Builder Central, and then select Builder Central.
- In the Builder Central Availability section, turn on the toggle.
-
Give each admin and builder the Access Builder Central user
permission.
Assign it through a permission set, which is the recommended way to grant access and is easy to remove when your evaluation ends.
-
On the Builder Central Setup page, select Open Builder Central.
To return later, open the App Launcher, then search for and select Builder Central.
Builder Central is now available to the users you assigned.
The org switcher in the top-right corner shows the org you're currently working in and whether it's a sandbox or a production org. Select it to switch to another connected org or to connect a new one, much like switching orgs from your profile in Salesforce. When you switch, Builder Central reloads in the org you choose and opens your workspace there. Your workspace and projects are scoped to you: they're yours alone and aren't shared with other users in the same org, and switching to another org doesn't carry a project over or deploy your work there. For example, you can move from one Developer sandbox to another to work on projects in each. You build in a sandbox and publish to that same sandbox.
You can build and design in any org, including a production org. What changes by org type is preview and publishing. To open a preview org with Preview, use a Developer or Developer Pro sandbox. Production orgs, Developer Edition orgs, and full and partial copy sandboxes don't provide preview orgs, though the in-app Design preview works in any org. The Publish to Sandbox button appears in sandboxes. In a production org, there's no Publish to Sandbox button, but you can ask the Build Agent to deploy your work. For full functionality, including preview orgs, work in a Developer or Developer Pro sandbox.
