VC: Knowledge Base

[SimoneZaza]

Description

The current entanglement between a VC and a Space creates conceptual confusion, making it challenging for users to understand each concept independently. This coupling leads to multiple UX issues, reducing overall usability and creating friction in navigation and understanding. By decoupling VC and Space, we can streamline the user experience, making both concepts more intuitive.

Goal

• Intuitive 'location' for the body of knowledge of a VC
• Separating VC from Space (which are for example causing problems for users who have the privilege to create vcs, but with a space without the right entitlements)

Hypothesis

• Separation from Space will lead to less confusion about the VCs

Must have scope

• Separate KnowledgeBase entity, and usage of that entity instead of a Space

To discuss:

• visibility of the content of Knowledge Base
• who should have rights to update the content of the knowledge base? By default picked up from edit rights on the VC
• migration path

PLUS

• usage of KnowledgeBase entity within a Space?

Stakeholders

Product, Sales

Design

Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us