- Ya
- 12 Agosti 2026, 22:13 UTC
- Mwandishi
- kamo
- Ahadi ya
- c63d261
Every tab on /account/view/{id} is a real route now — /members, /history and the rest are links somebody can send, bookmark, or land on. Old ?tab= links redirect to the matching one. Each tab loads its own data, so opening an account no longer waits on every tab's data before showing any of it. Add Member opened a "coming soon" toast. It now opens the same picker the Manager field uses, searching every member of the organization rather than only staff — the person paying for an account is frequently not on the payroll. People already on the account stay visible but unpickable with the reason, because a name that is simply missing from a search reads as a broken picker. Set-as-primary and remove work too, remove behind a confirm that says what it does and does not delete. Both the table and the picker mark which kind of person each row is. Without it a member and a team member read identically and the list quietly implies everyone on it works here. The member rows also render at all now: the type claimed keys the endpoint has never sent, so every name showed "---" and nothing could be removed — the row id the remove call needs was one of the invented fields. The lead view's history panel becomes EntityHistoryPanel, shared with the new account History tab: same filters, same paging, same empty states. What stays with each caller is only where the feed comes from and what its ids mean.