Core concepts
Six words the rest of the documentation assumes you know.
Context
One piece of content — a file, a wiki page, a ticket, a conversation. Contexts are what search returns. Each one keeps its history, so you can see what changed and when.
Source
A connected system that produces contexts: a repository, a wiki space, a project, a channel. Also called a connector. Sources sync on a schedule and keep their contexts current.
Memory
A note an agent writes for later — a convention, a gotcha, a "we do it this way because…". Memories are advice, deliberately separate from contexts, which are source material. Useful memories rise; unused ones fade.
Organization
Everything belongs to one. Users, sources, contexts and memories are scoped to it, and nothing crosses between organizations.
Owner
Who can see a context. Content with no owner is visible to everyone in the organization. Content with an owner is visible only to that person — including to administrators, who manage the system without being able to read private content.
Access profile
A way to share specific sources with specific people, without changing anyone's role. This is how you give someone access to one repository rather than to everything.
The two that trip people up are owner and access profile — they are how visibility actually works, and roles matter less than most people expect. See Content visibility.