Learn about CMS Workspaces, Channels, and Contributors
After completing this unit, you'll be able to:
- Describe the purpose of a CMS Workspace.
- Add a publishing channel to the CMS Workspace.
- Define the contributor roles in a CMS Workspace.
- Add languages to the CMS Workspace.
A Container for Content
Chris, the Tucker Home Goods admin, is eager to help her content experts, Sheng and Elle, get up and running on the Salesforce CMS. The first thing Chris has to do is set up a CMS Workspace in the app. CMS Workspaces are the primary organizing and security principle in the Salesforce CMS app. Each CMS Workspace consists of one or more publishing channels, which can be Experience Builder sites that share content created by one or more contributors to the workspace. CMS Workspaces can differentiate between internal and external information, different geographies, or even different campaigns. The organization structure is only limited by your imagination. CMS Workspaces also help control access to the content.
An org can have various workspaces, each with different publishing channels, content, and contributors. CMS Workspaces give you granular control over who’s creating content and where the content is shared.
Add a Publishing Channel for CMS Content
After creating the CMS Workspace, our trusty Salesforce admin’s next task is to add a publishing channel. For now, the only channel in the org is the Tucker Home Goods Experience Builder site that she set up earlier. Chris can add other publishing channels, such as the B2B commerce site, mobile app, or marketing emails, to distribute content in the future.
To add a channel in the CMS Workspace, she simply clicks Add Channel and chooses the Tucker Home Goods’s Experience Builder site, and voilà!
Add Contributors to the CMS Workspace
As a part of creating the CMS Workspace, Chris wants to add contributors who will help create and manage the content within the workspace. Chris has plenty to do as the Tucker Home Goods Salesforce admin. Delegating content creation and management to her coworkers is an opportunity she’s not about to pass up.
There are three 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 Salesforce CMS app access (including all workspaces); control over all site and digital experiences settings; and can create Experience Builder sites, apps, and email templates. The admin works in Salesforce Setup, the Salesforce CMS app, and the site or community’s Builder and Workspaces settings.
Content admin (Sheng)
These contributors have access to all content in the CMS workspace and can manage contributors and content sharing. Content admins do the bulk of the work in the CMS Workspace.
Content manager (Elle)
These contributors have full access to all content in the CMS workspace. The content managers do their work in the CMS Workspace.
Chris adds Sheng as a content admin to the newly created workspace, and adds Elle as a content manager. Once she’s created the workspace and the contributors, Chris hands over the reins to Sheng, who has full control over the workspace as the content admin.
As the content admin, Sheng can add contributors, channels, and languages to the CMS Workspace without asking Chris to do that for him.
As the content manager, Elle can write and publish new material, and mark content for translation.
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. As part of the CMS Workspace setup, Chris chooses English, Brazilian Portuguese, and Japanese as the workspace languages, and selects English as the default language. This helps content creators to flag content for translation and upload translated content into the app.
- Salesforce Help: Role-Based Access in Salesforce CMS