Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Experience Builder entry
How-to guide

How to set up Experience Builder in Salesforce

Experience Builder is the visual page editor for Experience Cloud Sites — drag components, set theming, configure pages, manage navigation. Each Experience Cloud Site has its own Experience Builder. Setup happens once per site at site creation; iteration happens here.

By Dipojjal Chakrabarti · Editor, Salesforce DictionaryLast updated Apr 20, 2026

Experience Builder is the visual page editor for Experience Cloud Sites — drag components, set theming, configure pages, manage navigation. Each Experience Cloud Site has its own Experience Builder. Setup happens once per site at site creation; iteration happens here.

  1. Open Setup → All Sites → click into a site → Builder

    Setup gear → Quick Find: All Sites → click Builder for the site you want to edit.

  2. Drag components onto pages

    Left rail: standard + custom components. Drag onto regions on the canvas.

  3. Edit component properties on the right rail

    Each component has its own property panel — content, visibility, behavior.

  4. Configure theming via the Theme panel

    Brand colors, fonts, logo, layout. Apply globally or per-page.

  5. Manage Audiences for visibility rules

    Audiences tab → New Audience. Define rules (User Profile = X, Permission Set = Y) for component / page visibility.

  6. Configure navigation menus

    Settings → Navigation Menus → drag pages and external links into the menu.

  7. Click Publish

    Publishes changes live. Until Publish, your edits are draft-only and invisible to site visitors.

Key options
Component libraryremember

Standard, custom Lightning Web Components, AppExchange components.

Themeremember

Brand colors, fonts, layout. Per-site.

Audiencesremember

Visibility rules — User Profile, Permission Set, custom criteria.

Navigation Menusremember

Page order in the site's nav.

Aura vs LWRremember

Locked at site creation. Aura: more components. LWR: faster, fewer components.

Gotchas
  • Experience Builder edits are draft-only until Publish. Forgetting to Publish is the #1 source of "my changes aren't showing up" tickets.
  • Aura and LWR use different component libraries. A component that exists in one may not exist in the other — the Builder's left rail filters automatically.
  • Audiences cascade — a page with Audience = X and a child component with Audience = Y both apply. Misaligned Audiences hide content unexpectedly.

See the full Experience Builder entry

Experience Builder includes the definition, worked example, deep dive, related terms, and a quiz.