Skip to content

Knowledge and Memory

Spaces can narrow what the tenant platform agent knows for a particular workroom. Knowledge bases bring authored source material into the Space. Memory captures retained facts and observations that belong to that Space’s history.

This keeps context local. A support Space can use support runbooks, a customer Space can use customer documents, and an internal finance Space can retain finance-specific lessons without making every other Space inherit them.

Knowledge bases are operator-curated document sources. Assign them to a Space when the agent should be able to retrieve from that material while working there.

Good Space knowledge-base candidates include:

  • Customer documentation.
  • Product or policy runbooks.
  • Project plans and operating docs.
  • Department-specific source material.

The Admin KBs tab controls which knowledge bases are selected for the Space.

Memory is retained knowledge from prior work. Space-scoped memory should answer “what has this workroom learned?” rather than “what is true for the whole tenant?”

Use Space memory for observations, preferences, and facts that should follow future work in the same Space. Use tenant-wide Memory or agent workspace files for broader facts that should apply across Spaces.