- Ya
- 8 Agosti 2026, 17:30 UTC
- Mwandishi
- kamo
- Ahadi ya
- 268b6f8
The tab loaded every organization in one request and rendered a card each, with the backend fanning out per org, then per account, then per subscription. Search, sort, filter and paging now run server-side against the whole estate, so the page cost is flat no matter how many organizations exist. The row is also the right object now. A subscription is HELD by an account and TARGETS an org, so the old card -- keyed on the holder -- had to print the target's name inside a nested table, and customer orgs appeared as strings inside other orgs' rows rather than as rows. Each row now carries entitlement (inbound: what governs this org) and billing held (outbound: what it bills for others) as separate facets. Design: a status rail down each row's left edge and a proportional estate bar, so a page reads as a colour histogram of commercial health before a word is read; tabular numerals with zeros muted, since most cells on a billing estate are zero. Table state lives in the URL so a filtered view is linkable -- written through a copy that preserves `tab`, and without publishing activeTab, which belongs to tabSync.