Add knowledge and memory context to AI employees
Use the knowledge base for stable reference material and let memory capture accumulated user facts and patterns over time.
Knowledge base vs memory
Knowledge base: durable reference material you deliberately provide.
Memory: accumulated user facts, preferences, and patterns the system extracts over time.
Use the knowledge base for business rules, terminology, project context, and domain-specific instructions.
Knowledge-base behavior
Each employee has its own knowledge base.
It is stored per employee and editable in the UI.
It is used across conversations.
Previous knowledge versions are saved to history before overwrite.
Conversation visibility and support phrasing
Employees are workspace-shared, but personal conversations remain user-scoped by default.
Delegation audit threads are hidden from normal conversation lists.
Empty stale personal conversations may be cleaned up after long inactivity.