Feature
When your network sits inside a company, map it clearly.
Optional org chart when your world is a company.
Optional relational org layer.
Optional structure for employers and programmes: companies, teams, and people in a hierarchy—alongside rich personal records, not instead of them.
Add companies, teams, and who reports to whom—next to normal person notes, not instead of them.
Company → Team → Person assignments with optional reports-to edges. Org fields are additive; Person remains the primary record for notes and history.
Org & reports-to on Mac (screenshot coming soon)
Org & reports-to on Mac (screenshot coming soon)
Org & reports-to on Mac (screenshot coming soon)
Why it matters Why it matters Data model & behavior
- Companies and nested teams
- Clear hierarchy: Company → Teams → People
- Reports-to outlines and org-oriented navigation on Mac
- Companies and nested teams
- Hierarchy from company down to people
- Reports-to views on Mac
- Hierarchical team trees
- Person.teamIds / company linkage in the local schema
- Mac reports-to outline view over the same graph
How teams use it In practice Implementation notes
Use org mapping when politics and reporting lines matter; skip it when your world is mostly clients and friends.
Assign people to teams so filters and dashboards can align with structure when you want that lens.
Turn it on when structure matters; ignore it for a mostly social network.
Teams can drive filters when you want that lens.
You can run a people-only workflow with org tables unused.
Filters can key off team membership when populated.