---
schema_version: "1"
id: e094d7ce6c282451a7b9755054a9233a5e6546783fac1f767cfae3e9afdfbcc3
title: Set Up Builder Central (Beta)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/builder_central_set_up.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.builder_central_set_up.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7a1edc3b206dfa7b59973143d0c8511cef88cacc096476e1e25b04e580d196f5
description: 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.
products:
  - Salesforce Platform
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Foundations or Agentforce 1</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d1861e73">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">To turn on Builder Central</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">Customize Application</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">To build apps in Builder Central</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">Access Builder Central</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">To assign the Access Builder Central permission to others</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d1861e73 ">Assign Permission Sets, or Manage Users</td>

          </tr>
        </tbody>
      </table>

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](https://help.salesforce.com/s/articleView?id=ai.generative_ai_enable.htm&type=5&language=en_US). Until Einstein is turned on, the **Access Builder Central** user permission doesn't appear, so you can't assign it to your builders.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-builder_central-264-0-0-production-enus/b289b805-9f02-4038-93a5-7ae3a6138aac/images/icon_important.png)

Important When you clone a sandbox, not all org settings carry over, including the Einstein setting. If the **Access Builder Central** permission isn't listed in a cloned sandbox, turn on **Einstein Setup** again, and then assign the permission.

1. From Setup, in the Quick Find box, enter Builder Central, and then select **Builder Central**.
2. In the **Builder Central Availability** section, turn on the toggle.
3. 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.
4. 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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-builder_central-264-0-0-production-enus/b289b805-9f02-4038-93a5-7ae3a6138aac/images/icon_note.png)

Note To help the Build Agent generate higher-quality metadata for complex builds, such as data models, flows, and permission sets, turn on the **Metadata Experts MCP** server. This Salesforce-hosted server gives the Build Agent added Salesforce-specific expertise. It's optional but recommended. On the Builder Central Setup page, in the **Metadata Experts MCP Server** section, select **Set Up Metadata Experts**.

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.

#### See Also

- [Builder Central (Beta) Permissions](https://help.salesforce.com/s/articleView?id=platform.builder_central_permissions.htm&release=264.0.0&type=5 "Beyond the base access that turns on Builder Central and lets a user build, some apps need extra access, such as a license or add-on, based on what your app includes, such as generative AI features or an agent.")
- [What You Need Before You Build](https://help.salesforce.com/s/articleView?id=platform.builder_central_what_to_bring.htm&release=264.0.0&type=5 "Builder Central builds for you, but the best results come from the context you provide. This context is optional, and you don't need it all up front. You share most of it as you describe and refine your app, not in your first prompt.")