Salesforce CMS workspaces, channels and content
How Salesforce CMS content reaches a site: enhanced CMS workspaces with the site added as a channel, matching default languages, contributor roles for users and public groups, drafts, publishing and scheduling, trusted URLs for external images, CMS Connect for an external CMS, conditional collections and content pages on Aura sites, and data binding on LWR sites.
Implement Salesforce CMS content into an Experience.
~8 min read · 11 practice questions ·
What the exam expects
- Connect a site to Salesforce CMS by adding it as a channel of a workspace, and match the workspace and site default languages.
- Assign contributor roles per workspace to users or public groups.
- Explain drafts, publishing, scheduled publishing and how a new version replaces live content.
- Fix external image or document links with Content Security Policy trusted URLs, and use CMS Connect for content kept in an external CMS.
- Display content on Aura sites with conditional collections and CMS content pages, and on enhanced LWR sites with the Grid component and data binding.
Key terms: CMS workspace (where content is authored, with its own contributors, languages and channels; new ones are enhanced); channel (a destination, such as a site, that receives a workspace's published content); contributor role (content admin, content manager or content author, set per workspace); CMS Connect (a connection that renders content from an external CMS in a site); data binding (LWR expressions that fill a component with CMS or CRM data).
Key facts
- Detail
- Add the site as a channel, then publish content, before using it
- Detail
- Every new workspace since Winter '25
- Detail
- Up to 2,000 CMS workspaces per org
- Detail
- Can't be changed; should match the site's
- Detail
- Content admin or content manager
- Detail
- Users or public groups, role set per workspace
- Detail
- Replaces live content in all channels when published
- Detail
- Add the domain to CSP trusted URLs
- Detail
- Component Path holds only the part after the root path
- Detail
- Up to 10 filters; one Topic filter
- Detail
- One per content type, CMS Single Item (Detail)
- Detail
- Shows CMS collections only in enhanced LWR sites
Sources for this section (9)
- Custom Site Pageshelp.salesforce.com (opens in a new tab)
- CMS Workspaceshelp.salesforce.com (opens in a new tab)
- Publish CMS Contenthelp.salesforce.com (opens in a new tab)
- CMS Roleshelp.salesforce.com (opens in a new tab)
- CMS Contenthelp.salesforce.com (opens in a new tab)
- CMS Connecthelp.salesforce.com (opens in a new tab)
- Conditional Collectionhelp.salesforce.com (opens in a new tab)
- CMS Single Itemhelp.salesforce.com (opens in a new tab)
- LWR Componentshelp.salesforce.com (opens in a new tab)
- Why does a site manager see no workspace content in Experience Builder even though items are published?
- When do edits to a published item reach the site?
- Why do externally hosted CMS images raise security alerts on a site?
- Which role lets a public group publish content but not manage contributors?
- Which LWR component shows a paginated CMS collection from an enhanced workspace?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Experience Cloud Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the Experience Cloud Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams