A knowledge graph for teams: how connections replace folders
knowledge
Why linking knowledge by topic, client, and project works better than folder trees, and how a team knowledge graph behaves in practice.
Folders ask people to decide, in advance, where something belongs. A knowledge graph asks a different question: what is this connected to?
The problem with folders
- One file often belongs in several places.
- Structure drifts as people file things differently.
- New teammates have to learn the system before they can use it.
How a knowledge graph works
In Constella's knowledge graph, saved items are linked by topic, client, and project. A quote PDF connects to the client, the pricing page it drew from, and the project it supported. Ask about one and the rest is reachable.
What this changes day to day
- Retrieval: you search by what you remember, not where you put it.
- Context: related material appears alongside the item you open.
- Answers: reasoning search uses those connections to give cited answers.
- Onboarding: new people query the memory instead of learning a folder map.
What it doesn't do
A graph doesn't replace judgment. You still check the cited source, and permissions still decide who sees what. See trust and controls.
Watch the explainer: A knowledge graph for teams. To see how it fits a team, visit Constella for teams.