Contacts and Companies
Companies are folder-backed workspaces. Contacts are records for people, with explicit links to companies and optional workspace folders.
What that means in practice
- each company can own related files, notes, chats, tasks, and other artifacts
- each contact can link to companies, workspaces, and related context without pretending the person is a folder
- the views present relationship data as structured lists without turning it into free-form notes
Common scopes users see
The explorer views commonly expose:
AllMyRepo
Those scopes help users switch between shared entity work and their own private or personal-ownership context.
Why this matters
If teams keep companies as workspaces and contacts as clean records, they gain:
- better search and handoff behavior
- less duplicate stakeholder tracking
- clearer ownership for related documents and conversations
Guardrails
- keep one canonical entity per real person or company
- create contact workspaces only when there is real person-specific work to store
- retire duplicates quickly
- do not fall back to free-form notes when an entity view is the correct model