Design Usage Limits and Quotas

Collaboration & Enterprise · enterprise, pricing, status

Updated 2026-07-28

Put usage where the work happens. A quota that only exists on the billing page is discovered at the moment it blocks someone.
Show consumption as a proportion of the allowance, with the reset date next to it. A raw number means nothing without the ceiling and the period.
Warn on a curve rather than at the wall. Notices at a comfortable margin, then close to the limit, then at it, give people time to act.
Tell the right person. The user who hits the limit often cannot change the plan, so the message needs both an action for them and a route to whoever can.
Degrade predictably at the limit, and say which behaviour applies. Queueing, slowing, blocking new work, or preserving read access are very different outcomes.
Never destroy data because of a quota. Blocking new work is acceptable, and deleting existing work to enforce a limit is not.
Show the history so spikes can be explained. "Which day caused this" is the first question anyone asks about an unexpected bill.
Make the upgrade decision informed by naming the new limit and the new cost, rather than only linking to a pricing page.

Limits are a business rule, and the interface's job is to make sure nobody is surprised by one they could have planned around.