Companies

Companies at /companies is the client-organization directory: the companies the tenant does work for. Projects shows the company tree anchoring the project list — this workspace is that tree as its own surface.

• Tabs split the list: All Companies, Relationship Exists, and Primary - All. Search, sort, columns, filters, owner, and a type filter narrow the rows; Create Company adds a row.
• The table lists name, domain, city, state, and HubSpot owner ID per row, with domains linked.
• The HubSpot owner ID column ties each company to its CRM record: the directory here and the pipeline there share the same company, not two copies of it.

• Pick the company first; the work follows. Projects, deals, and contacts all hang off the company they belong to, so a missing or duplicated company row corrupts every list downstream.
• Each company carries its activity timeline: the notes, calls, and tracked emails attached to it in chronological order. The shared model lives on the Activities hub.

Owner

Each company names one owner, and the owner picker lists tenant members — not free text. Membership lives under People; if the company row and the member list ever disagree, People is the source of truth.

• The Company owner picker under About this company lists tenant members with a Search users filter: Anita Kaestner, Archer Preslhy, Chris McGovern, David Murray — plus an Unassigned row for clearing the holder.
• The record around the picker is the relationship context the owner holds: lifecycle stage cards, the engagement readout, the contacts rail, and empty deals, projects, proofs, and research rails.

• Company rows are shared facts, not per-project improvisation. Shared fields map across the hierarchy under Field Mappings — check there before adding a field the company level already carries.
• Views shape the list; the org default for the views the team opens daily is set under Table Views.

What next

• Activities: the shared activity model behind each company timeline.
• Sites: the company-child locations under each company.
• Projects: the project hierarchy under each company.
• Contacts: the people at these companies.
• Sales deals: the pipeline per company.
• Field Mappings: the shared fields across the hierarchy.