Do you need to file a feature request?
Feature Request Description
I wanted to permanently save a text from the Co-Writer as a Notebook. The problem: if no Notebook exists yet, or if I want to assign it to a new one, I have to leave the current context. This interrupts the workflow and is not user-friendly.
In the Knowledge section, existing Notebooks cannot be deleted. Records cannot be moved between Notebooks or assigned to multiple Notebooks. However, processing operates at the Notebook level — not at the Record level. As a result, knowledge is locked into a single structural context and cannot be reused flexibly across different use cases.
Additionally, Records cannot be edited after creation. Once saved, they are immutable. This prevents iterative refinement or correction of knowledge and significantly limits maintainability and reuse.
Related Module
Dashboard
Use Case
No response
Additional Context
No response
Do you need to file a feature request?
Feature Request Description
I wanted to permanently save a text from the Co-Writer as a Notebook. The problem: if no Notebook exists yet, or if I want to assign it to a new one, I have to leave the current context. This interrupts the workflow and is not user-friendly.
In the Knowledge section, existing Notebooks cannot be deleted. Records cannot be moved between Notebooks or assigned to multiple Notebooks. However, processing operates at the Notebook level — not at the Record level. As a result, knowledge is locked into a single structural context and cannot be reused flexibly across different use cases.
Additionally, Records cannot be edited after creation. Once saved, they are immutable. This prevents iterative refinement or correction of knowledge and significantly limits maintainability and reuse.
Related Module
Dashboard
Use Case
No response
Additional Context
No response