Storage Quotas & Upload Limits: Evidence Needs a Meter

ITAD evidence is file-heavy: photos, certificates, signed documents, reports, support attachments, evidence packages. Storage cannot be invisible forever. At some point, the platform needs to know how much a tenant uses and what happens at the limit.

What counts

Tenant storage usage covers operational files in Supabase Storage: documents, photos, signatures, evidence and related uploads. Avatars live separately. Usage rolls up per tenant so package limits and admin storage views can talk about the same number.

Warnings

When usage approaches the configured quota, the platform can send a storage warning notification. That gives admins time to review usage, upgrade the package or clean up legitimate mistakes. Evidence should not fail because nobody noticed the meter blinking.

Upload blocking

When a tenant exceeds quota, new uploads can be blocked on guarded paths. The block is explicit: the user sees that storage is the problem instead of a mysterious upload failure. Mysterious upload failures are how support queues grow teeth.

Admin view

/admin/storage gives platform staff a cross-tenant view of usage and quota. Tenant billing settings show the tenant-facing package context. Together they connect technical storage with commercial limits without turning every PDF into a finance debate.