Store reference documents for editorial work inside KB structure
backlog
N
Nearby Cheetah
We store internal documents (like internal glossary and administrative stuff) inside a hidden category directly in the KB. I would find it useful if there was a dedicated repository for internal editorial reference documents that can be accessed directly from within the KB structure or navigation. These documents need to be easily accessible (as few clicks as possible) for productive work. They should be live-editable, but don't need a publication workflow.
Log In
D
D360 Product Management
marked this post as
backlog
N
Nearby Cheetah
Hi Mohamed! I'm including a screenshot to show you our setup ("Redaktionsarbeit" is our category for editorial documents). We found that when editorial documents are stored outside of Document360 (like in Confluence), they are more likely to be forgotten than if they are right there in our documentation tool. I would imagine a standalone repository that is dedicated to these types of documents. But it would be integrated somehow into the KB structure so that it can easily be accessed - perhaps even from within an article. These documents should be editable just like regular articles, but without a publication workflow. Does that make sense? Thanks! Claus
Mohamed Shakheen
Nearby Cheetah: Hi Claus,
Thanks for sharing the context and the screenshot - that helps clarify the setup and the underlying problem very well.
Your point is well taken: keeping editorial and internal reference documents within the same ecosystem as the knowledge base significantly reduces the risk of them being overlooked, compared to maintaining them in an external tool like Confluence. The idea of a dedicated, standalone repository that is tightly integrated with the KB structure - accessible from within articles and editable like regular content, but without a publication workflow - is a coherent and sensible direction.
At this stage, this is not something we have actively prioritized on the roadmap. That said, we do see clear value in the use case you’ve outlined. We’ll continue to evaluate this based on broader customer traction and similar requests, and if we see sufficient demand, we can consider prioritizing it for a future roadmap cycle.
Mohamed Shakheen
Hi Nearby Cheetah
Thank you for sharing this feedback.
To ensure we fully understand your workflow needs, could you clarify whether you're envisioning this internal repository as a standalone workspace separate from the KB hierarchy, or as an integrated panel within the existing KB navigation where editors can quickly access and maintain internal reference documents?
This will help us evaluate the right approach.