Kodori has no folder tree. Instead, Collections give you the organizational metaphors of legal matters, AEC projects, accounting clients, or whatever your firm's vocabulary is — without the duplicate-files problem of a literal directory structure.
A Collection has:
- a kind (cabinet / drawer / folder / project / matter / custom) - a name and optional description - pinned members (documents you explicitly add)
Add a document to a Collection from the document page or the Collection page. The same document can sit in any number of Collections without storage duplication — the bytes only live in one place, addressed by their content hash.
Create one from /collections/new, or after a folder upload — Kodori offers to create a Collection seeded with everything you just uploaded.
## Matter timeline
Every Collection has a "Timeline →" link in its header. /collections/<id>/timeline aggregates every event from every document pinned to the Collection PLUS the Collection's own events (member-added, member-removed, rule-updated, permission-granted) into one chronological narrative.
- Day-grouped: each event lands under a sticky date header, newest first - Color-coded by event tone: red for DLP / anomaly, amber for legal-hold / retention / purge, emerald for create / version / annotation, blue for permission / collection-grain - Filter chips computed from the in-page slice — only event types that ACTUALLY appear in this matter render as options - Permission-trimmed: documents you can't read drop from the doc-event side; collection-grain events stay (you're already on the collection page) - Capped at 250 events per render — older history lives on /audit
When to use which audit surface: - /doc/<id> History — "what happened to this one document" - /collections/<id>/timeline — "what happened on this matter" - /audit — "what happened in this tenant" (full filter set + CSV export)