Learn about CMS Workspaces, Channels, and Contributors
Learning Objectives
After completing this unit, you'll be able to:
- Describe the purpose of a CMS workspace.
- Add a publishing channel to a CMS workspace.
- Define the contributor roles in a CMS workspace.
- Add languages to a CMS workspace.
A Container for Content
Chris, the Tucker Home Goods admin, is eager to help her content experts, Sheng, Elle, and Calvin get up and running on the Salesforce CMS. The first thing Chris has to do is set up a CMS workspace in the Digital Experiences app.
To follow along, scroll down to the Challenge section and click Launch to open your Trailhead playground. You can create a new playground just for this hands-on challenge, or you can use an existing one. Whichever you choose, ensure that Digital Experiences is enabled.
- From Setup, enter
Digital Experiencesin the Quick Find box, then select Settings. - Select Enable Digital Experiences.
- Your digital experiences domain is shown under Domain preview. It includes your My Domain name in the format
MyDomainName.my.site.comfor production orgs. - Click Save, then OK.
Now that Digital Experiences is enabled, let’s dive into the app and create an enhanced CMS workspace.
- In the App Launcher, enter
Digital Experiencesin the search bar, then select Digital Experiences Home. - Click Create a CMS Workspace.
- Name the workspace
Website Contentand add a brief description. - Select Enhanced CMS Workspace and click Next.
- You can add channels now or skip this step. We won’t check for channels in the Hands-on Challenge, so click Skip.
- Set the default language to English, then click Finish.
And that’s it! The foundations are ready for Tucker Home Goods’s enhanced CMS workspace.
An org can have multiple workspaces, both enhanced and non-enhanced, each with different publishing channels, content, contributors, and languages. Some orgs need just a handful of workspaces and others need hundreds. You can create workspaces for different audiences, geographies, campaigns, for internal or external information, and more. The organizational structure is only limited by your imagination.
Tucker Home Goods is just getting started in Salesforce CMS, so Chris is satisfied with the enhanced CMS workspace for now. This workspace will be the hot spot for Sheng, Elle, and Calvin when they create content about their products.
Add a Publishing Channel for CMS Content
Tucker Home Goods has an enhanced LWR site where they sell and promote their products. In order to share CMS content on this site, Chris must add the site as a publishing channel to the enhanced CMS workspace. She simply goes to Channels in the workspace settings and adds the enhanced LWR site.
In the future, Chris can add other publishing channels to the enhanced workspace, such as another site or a public channel for a mobile app to distribute content to other audiences. If Chris chooses to add another site, she can only add an enhanced LWR site because enhanced CMS workspaces don’t support Aura site channels.
Add Contributors to the CMS Workspace
As a part of creating the enhanced CMS workspace, Chris wants to add contributors who will create and manage the content within the workspace. Chris has plenty to do as the Tucker Home Goods Salesforce admin including designing and building the entire site. So delegating content creation and management to her coworkers is an opportunity she’s not about to pass up.
There are four different roles that can access the CMS workspace, all with different permissions. Here they are, from most to least access.
Salesforce Admin (Chris)
A Salesforce admin has full Digital Experiences app access, including all CMS workspaces; control over all site and digital experiences settings; and can create Experience Builder sites and apps. The admin can also create and manage CMS workflows and approvals for individual enhanced CMS workspaces. The admin works in Salesforce Setup, the Digital Experiences app, and in the site settings or Experience Builder.
Content Admin (Sheng)
These contributors have access to all content in the CMS workspace. And they can also manage other contributors, channels, and publishing. Content admins can further delegate roles and responsibilities in the CMS workspace as needed.
Content Manager (Elle)
These contributors have full access to all content in the CMS workspace, including publishing and managing content translations. They can also review content submitted through the Basic Approval Request workflow in enhanced CMS workspaces.
Content Author (Calvin)
These contributors can only create, edit, and view content in the CMS workspace. They can submit their content through the Basic Approval Request workflow in enhanced CMS workspaces. Content authors can’t publish or unpublish content.
In the enhanced workspace, Chris goes to 
| Contributors and adds Sheng as a content admin, Elle as a content manager, and Calvin as a content author.
After she’s created the workspace and added contributors, Chris hands over the reins to Sheng, who now has full control over the enhanced workspace as the content admin. Sheng can add additional contributors, channels, and languages to the CMS workspace without needing to ask Chris to do that for him. And Elle and Calvin can help with writing and managing new material.
These contributors and roles are unique to this particular enhanced CMS workspace. If Chris ever decides to create additional CMS workspaces for Tucker Home Goods, she can add different contributors and assign different roles. For example, if Elle owns all of the content about furniture, Chris can create a new workspace specifically for content about furniture. And she can designate Elle the content admin of that workspace.
Add Languages to the CMS Workspace
Tucker Home Goods has a strong presence in Brazil and Japan, so having localized content is a key part of the Salesforce CMS implementation. In the workspace, Sheng goes to 
| Languages and adds Brazilian Portuguese and Japanese to the workspace. By customizing and adding languages to the workspace, Sheng lets contributors flag content for translation and upload translated content into the workspace.
