Examples of Content Collections

Team or Department

Your company’s teams and departments have different responsibilities and learning needs. For example:

• Members of your Sales team want to learn about sales processes, ethical communication with potential customers, and growth opportunities in their team. Create a Sales team content collection, and enable access to the collection from a permission set that’s assigned to Sales team members.
• Members of your Support team want to learn about case management, product enablement, and growth opportunities in their team. Create a Support team content collection, and enable access to the collection from a permission set that’s assigned to Support team members.

Discipline or Job Function

Your company’s teams consist of specialists, and each specialist fulfills a unique skill, but they all function together as a business unit. In this case, maybe you want to deliver content targeted to each specialized role, so that all teams across the company operate consistently. For example, your company has two teams, and each team consists of these specialized roles.

• A writer that wants to learn how to produce content. Create a Writers content collection, and enable access to the collection from a permission set that’s assigned to writers from both teams.
• An engineer that wants to learn how to develop and test products. Create an Engineers content collection, and enable access to the collection from a permission set that’s assigned to engineers from all teams.
• A manager, who wants to learn how to assign tasks and track progress. Create a Managers content collection, and enable access to the collection from a permission set that’s assigned to managers from all teams.

Geographic Region

Learners in one part of the world can have different cultural or language-specific requirements. For example, maybe you want to make certain content available to teams in North America, and other content available to teams in Europe. You can create separate content collections and associated permission sets for each region.

Note Segmenting content collections by geographic region is different than localizing content for other languages. When you localize existing content, you’re adding languages to the same content, in the same content collection, that you’ve already published. For example, you can’t assign the English version of a module to one content collection and the French translation of that same module to a different content collection. Instead, create unique modules for each audience. To learn more, see Considerations for Languages on Your Enablement Site.

Relationship to Your Company

Your company can develop learning content for internal team members and external customers or partners. You can ensure that internal learners access only internal-facing content and external learners access their appropriate content. For example, let’s say that you want to support different content for these audiences.

• Internal learners at your company who want to learn their responsibilities for participating in an upcoming customer-facing event. Create an Internal Employees content collection, and enable access to the collection from a permission set that’s assigned to internal learners.
• External customers who want to learn about what they can do at your company’s event. Create an External Customers content collection, and enable access to the collection from a permission set that’s assigned to external customers.

Important To implement this particular example, your enablement site must use Trailblazer.me (TBID) for user authentication and must enable access for members of an Experience Cloud site. If your site uses Salesforce Identity for Enablement for user authentication, it’s difficult to support a combination of internal and external users. With Salesforce Identity for Enablement, we recommend that you restrict your enablement site to either internal or external users, but not both. For more information, see Enable External Learners for Your Enablement Site.

Other Criteria

Here are a few more ways that you can segment your content collections.

• By regulatory compliance, such as content collections specific to learners who must comply with healthcare or safety requirements
• By participation in a project, such as content collections specific to onboarding for a special product or event

Note You can create up to 100 content collections.

Shared Content and Stacked Content Permissions

Content collections can help you implement solutions where groups of learners can access both their own content and shared content. Permission sets stack, and a user’s cumulative permissions depend on all the permission sets assigned to them. For any content that you want to make available to multiple audiences, create a content collection specifically for your shared content.

For example, what if you had separate content for your Regulatory Compliance team and the Customer Support team, but you wanted to allow both teams to access some shared content? Create these content collections and associated permission sets:

• Create a Regulatory Compliance content collection and permission set, and add Regulatory Compliance team members to the permission set.
• Create a Customer Support team content collection and permission set, and add Customer Support team members to the permission set.
• Create an All Employees content collection and permission set, and add both Regulatory Compliance team and Customer Support team members to the permission set.