Knowledge is the organization’s descriptive layer: what it knows, refers to, or uses as evidence. A Source can be a note, Q&A, file, website, web page, or synchronized item. Sources live in a library that people can browse and Agents can retrieve from.
Add
Choose the Source type that matches the material.
Organize
Place Sources in Areas people recognize.
Process
Wait for imported content to become ready.
Use
Attach Knowledge directly or through an Area.
Work by task
- Add a Source for notes, Q&A, and files.
- Add a website to crawl a site into managed Web page Sources.
- Organize Sources into an Area tree built for browsing.
- Set Knowledge ownership when someone should maintain a collection.
- Understand Source status before trusting imported material in answers.
Knowledge does not become a rule
Importance does not make a Source authoritative. If the organization has decided that people must follow something, create a Standard. Keep supporting manuals and evidence as Knowledge and link them.
Areas are where Sources live
An Area holds Sources, referenced Standards and Connectors, and it nests. An Area with neither a description nor instructions is what the product shows as a folder — the same row, invisible to an Agent's routing because there is nothing to route on.
How a Source becomes usable in answers
Adding a Source starts an ingestion process. Tindre reads the material, records a revision, and prepares a retrieval projection that Agents can search. Imported does not always mean ready: check the Source status before relying on it, especially after replacing a file, changing a website, or seeing a failed crawl.
An Agent still needs the relevant Knowledge in scope. Attach the Source or its collection directly to the Agent, or include it through an active Area. The caller’s access and the boundary of the door they came through are applied when the question is answered.
Areas, ownership, and access solve different problems
Areas help people browse and keep related Sources together. Ownership identifies who should maintain the material. Access decides who may use it. Moving a Source into a well-named Area does not transfer responsibility or grant an Agent access by itself.
Organize around topics people recognize rather than mirroring every team in the organization chart. Name an owner when a collection needs active care. Review status and freshness when an answer cites material that appears outdated, then fix or replace the Source instead of compensating in the Agent instructions.