KamoCRM

One storage allowance, seats not users, and stop parsing prose

Fixkamo-marketing
Ya
27 Agosti 2026, 15:21 UTC
Mwandishi
Kamo
Ahadi ya
b29f8eb

Storage is 4 GB per seat on every plan. The cards need no special case to stop repeating it: ladderFeatures already shows a tier's delta over the one below, so making the four rows equal is what removes the line from Starter, Business and Enterprise. Enterprise loses "150 GB for the organization". StorageQuotaService reads only numeric_value and multiplies by seats, so that row was billed as 150 GB PER SEAT while the page promised a flat pool — the prose and the code disagreed and the code won silently. "Seat" everywhere a quantity is bought: the card headline, the period label, the comparison table, the JSON-LD offers and the fallbacks used at build time, which are what a cold deploy actually serves. PagePlan now carries seatCeiling and storageGbPerSeat as numbers. The calculator recovered both by running regexes over the rendered card copy, which made two English sentences load-bearing — and both sentences changed here. Each regex would have missed and fallen through to a stale default, on the one page whose entire job is to quote a number.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei