Skip to main content
Knowledge is where you build a reference library for your coworkers — documents and facts you add on purpose, so they don’t have to be repeated in every request. It’s self-serve: add something once in the console, and every coworker in scope can draw on it from then on.

​
Why this is different from Memory

Knowledge is what you deliberately curate and upload. Memory is what a coworker infers on its own as you work together. Both shape how a coworker approaches a task, but one is a library you stock, the other is something a coworker picks up along the way.

​
What you can add

Documents

Upload a background file — a brand style guide, a price list, an org chart, a briefing — up to 25MB, up to 20 documents. Every document needs a title and a description.

Websites

A URL worth knowing about, tagged as yours, a competitor’s, or just a reference, with a short note on why it matters.

Social profiles

A platform and handle — yours or a competitor’s — with a note on what to watch for.

Sources & guardrails

A named reference you trust, or a short standing rule like “always use metric units” or “never mention Competitor X by name.”
The description on a document matters more than it seems — it’s literally what a coworker reads to decide when that document is relevant to a task. A vague description means the document effectively goes unused. You get up to 100 structured entries (websites, social profiles, sources, and guardrails combined) per person.

​
Personal, or shared with your team

Everything you add starts out personal — visible only to you. Scope any item to a workspace instead, and it becomes team knowledge: every member of that workspace can see and manage it, not just the person who added it. That’s the difference between your own private notes and a shared reference library your whole team draws on.

​
Concrete examples

  • Upload your brand style guide once, and every coworker writes in your voice without you repeating it in every brief.
  • Add “always use metric units” as a guardrail instead of mentioning it in every single email.
  • Add your top three competitors as website entries, so Hannah always has them in mind without you naming them each time.
  • Add your org chart as a document so Elena understands who’s who when coordinating a project.

​
How this connects

Knowledge, Skills, and Memory all shape how a coworker approaches your work, in three different ways: Skills is how a coworker works a certain kind of task, Memory is what it’s learned about you, and Knowledge is what you’ve told it on purpose. See Hannah or Elena for coworkers whose work leans especially hard on background context like this.
Start small — one style guide or one guardrail is enough to feel the difference. Add more as you notice yourself repeating the same context across tasks.