Improve Conditional Content Functionality for Mixed Mode Public Articles
under review
Kesavan M
It would be beneficial to have conditional content functionality for public articles in mixed mode, similar to how Private Notes currently work. This would allow content to be dynamically displayed based on reader group access while keeping the article publicly accessible. Additionally, having clear visual indicators for such conditional content would help avoid misconfiguration. This enhancement would improve flexibility and usability for managing audience-specific content.
Log In
D
D360 Product Management
Hi Whole Wombat, Kesavan M
Thank you for the detailed feedback — this is a very important use case, and we completely understand the confusion and limitations you’ve highlighted.
What We’re Evaluating:
We are currently considering improvements in this area, with two key directions:
- Enable Conditional Content for Public Articles (Controlled Access)
Allow authors to:
- Keep articles publicly accessible
- Restrict specific sections within the article based on reader groups (login required)
This would bring true “mixed visibility within a single article”, which is a powerful and commonly requested capability.
- Improve Guardrails for Public Workspaces
At the same time, we also agree with your point around clarity and consistency:
- In scenarios where public = fully open access, reader group conditions should not create hidden or unexpected restrictions
- We are evaluating adding clear validation and messaging, such as:
“Reader group conditions are not applicable in public workspaces as all content is openly accessible.”
- Ensuring consistent behavior across standalone public projects and mixed projects
- Better UX & Visual Indicators
We also plan to improve clarity in the editor by:
- Clearly distinguishing conditional content vs private/internal notes
- Adding stronger visual indicators to prevent misuse
- Making it obvious when content is:
Public
Conditional (restricted)
Internal-only
Why this matters:
Your use case highlights a key gap:
Teams want flexible content control within a single article, without compromising the overall public accessibility.
This is something we see increasing demand for, especially in:
- SaaS documentation
- Tiered product documentation
- Customer vs partner vs internal segmentation
Next Steps:
We are actively evaluating:
- The correct product model for conditional content in mixed environments
- The right UX guardrails to avoid confusion
- Backward compatibility with existing setups
We’ll share updates here as we finalize the approach.
Thank you again for the detailed write-up — this is extremely valuable and directly shaping how we approach this improvement.
D
D360 Product Management
marked this post as
under review
W
Whole Wombat
Being unable to use conditional content in mixed-mode projects is a major drawback. Especially when it's enabled in the UI.
The benefits enable users to make articles public, while making certain elements require a login. This was a big feature we had planned to use, and it's very disappointing that it doesn't work as described.
Using the private note is a workaround, but it brings in other issues. Because the private notes are typically used for internal comments, using them for conditional content can be confusing. There isn't an easy way, aside from opening the special permissions, to know whether a private note is used internally or for conditional content.