How to control who can see and access content in Continu — the difference between hiding from Explore and locking access entirely.


Segmentation is the content-level control for visibility. Without it, content published in Continu is visible to anyone with broad content access. With it, you decide who can see the content on Explore — and optionally, who can access it at all.

The most important distinction: segmentation alone limits Explore visibility but doesn't block access. To make content fully private (so users outside the segment can't reach it even via direct link or assignment), check the Private box. This is the difference between "doesn't appear in browse" and "can't view, period."

For the strategic frame on content access and user management, see User Management: Who Has Access to What, and Why.


How to Segment Content

1. Navigate to the Audience tab. When creating or editing content, segmentation lives in the Audience tab. By default, segmentation is set to Off.

2. Toggle Segmentation On.

Segmentation toggle in the Audience tab

3. Add your segmentation requirements. Search and select attributes like Department, Location, Job Title, or custom fields. You can combine multiple criteria. Users who match all selected criteria can see the content on Explore.

Adding Segmentation criteria

4. Optionally, check Private. If checked, only users in the segmented audience can access the content at all — direct links from outside the segment don't work. Leave unchecked if the content should remain accessible (e.g., to learners who get assigned it through an Automation or Direct Assignment) but just not visible on Explore for the broader audience.


Private vs Not Private

Segmentation On, Private Off. Content is hidden from Explore for users outside the segment, but they can still view it if directly assigned, sent a link, or surfaced through search. Use for content that doesn't need to crowd Explore for irrelevant audiences but doesn't need strict access control.

Segmentation On, Private On. Content is hidden from Explore and blocked from access for users outside the segment. Use for confidential content, compliance-restricted material, or anything that genuinely shouldn't reach the wrong audience.

Segmentation Off (default). Content is visible to anyone with content access. Use only when the content is genuinely meant for everyone with platform access.


Configuration Pitfalls

Forgetting Segmentation Doesn't Block Access By Default. The most common segmentation mistake. An admin segments content thinking it's now private, but the Private box isn't checked. Users outside the segment still see the content if it's assigned to them or they have the link. Always check Private when access (not just visibility) matters.

Segmenting at the Track Level Only. Segmentation on a Learning Track doesn't override segmentation on the individual Content pieces inside it. If a learner has Track access but not Content access, they see the Track but can't complete it. Always verify segmentation on every Content piece inside a Track. See Add a Learning Track (Configuration Pitfalls).

Stacking Criteria Until the Audience Is Empty. Each additional segmentation criterion narrows the audience. Three or four layered criteria can result in zero matched users. Test by previewing as a user in the intended segment.

Forgetting to Set Segmentation on Sensitive Content. Compliance documents, internal-only decks, region-specific content published without segmentation is visible to everyone. Make the segmentation check part of every publishing review.

Using Segmentation as a Substitute for Smart Segmentation Rules. Content-level segmentation is one piece of the access model. For broader access patterns ("Sales team only sees Sales content"), use Smart Segmentation at the user/group level too. Content-level segmentation refines on top of that.


Where This Fits

You're here because you're setting visibility on a specific piece of content. The broader user-access model lives in User Management: Who Has Access to What, and Why. For the strategic frame on content visibility decisions, see Content Strategy: Designing Learning Assets That Scale.


See Also


Segmentation hides from Explore. Private blocks access. Check both decisions on every piece of content that isn't meant for everyone.

Was this article helpful?
1 out of 1 found this helpful