Conditional Content Block condition for author or team member context
N
Nutmeg Porpoise
Conditional Content Blocks currently support visibility conditions based on reader groups and login status. There is no condition type that targets the authoring or team member context - meaning content cannot be shown exclusively to portal users (team members, editors, admins) while being hidden from all public-facing readers, including those in reader groups, without using the separate Private Notes feature.
Add a Conditional Content Block condition that evaluates whether the viewer is accessing the article through the author portal rather than the public-facing Knowledge Base site. This would let authors embed work-in-progress content blocks — tables, sections, notes - directly within a published article, visible only when viewing from the portal, without requiring those blocks to live in the structurally separate Private Notes layer.
Benefit: Authors working on incremental updates within a live article can stage new content in place, review it in context alongside published content, and release it by simply removing or changing the condition - all without creating separate article versions or relocating content between the Private Notes area and the public body of the article.
Log In