- Shipped
- September 3, 2026 at 4:48 PM UTC
- Author
- Kamo
- Commit
- 9ce9c21
A record that is both an organisation and a person is named "Harmony Home Loans (Nickolas McGarry)" — the company leads, the contact qualifies. That rule lives in the browser's entityLabel(), so these endpoints stop picking one half and send both. - The /leads grid timeline stamped each entry with the contact and fell back to the company. Same lead, therefore, read as a person on its timeline and as a company on the grid that produced it. - The lead credit/assignment history resolved the contact only. Resolved here rather than in the shared history service because this is its only renderer, and one findAllById over the page's distinct leads is a single query. - An account's Leads tab was sending {uid, organizationId} and nothing else, so every column read "---" and every row linked to /leads/view/undefined. It now sends id (which is what that table keys and links on), the two name halves, status and dateCreated. The lead's e-mail is gated the way lead contact detail is everywhere else: your own lead always, anyone else's only with VIEW_LEAD_CONTACT_INFO_OTHERS.