Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Storage, capacity and expansion. TLS owners monitor physical storage observations, company file usage, capacity evidence and costs. Customer roles cannot open these infrastructure controls. Current availability: Recorded usage and planning budgets implemented; provider capacity requires verification.

Before you start. Owner access and agreed retention/export policies.

Step 1. Open /admin/storage as a TLS owner. Use the Owner storage pools and cost controls guide for measured sources, allocations, 75%/90% alerts and expansion.

Step 2. Read the measurement source. Database observations report D1 size metadata. Object usage is published after a complete resumable R2 scan. Company file usage sums recorded ticket attachments and documents; it excludes database rows and untracked objects.

Step 3. Obtain the actual provider allocation and record its evidence. Enter bytes, the 75% warning and 90% critical levels, and the current record revision. Save. Never enter an invented provider limit to make a percentage appear.

Step 4. Enter a monthly cost budget, decimal-GB storage rate, known fixed costs, attributed monthly revenue and target margin. The estimate covers only the costs entered, not unconfigured egress, operations, backups or taxes.

Step 5. Use Refresh observations to collect without sending email. Inspect the timestamp, source, stale-data state and scheduler result. The automatic production maintenance handler evaluates alerts on its configured five-minute schedule.

Step 6. Use Expansion plans to record requested capacity, a cost ceiling, reason, provider reference and verification evidence. Complete the actual provider operation and backup/restore acceptance before closing the change.

Step 7. Pause obsolete external inventory or move it to Trash. Restore within 60 days. A retention hold pauses inventory purge. This lifecycle changes the portal record; it never deletes a real database or bucket.

Now verify the result. Company and Managed IT customer accounts receive no capacity dashboard or API access. At exactly 75% the component warns; at exactly 90% it is critical. Unknown allocation remains unverified. A quota or budget edit does not create a provider purchase or customer charge.

If you get stuck. If usage is zero, compare database bytes with file metadata; they measure different things. A provider D1 database cannot be enlarged beyond its supported limit; capacity growth may require partitioning or migration. Missing native quota access remains an owner setup gate, not a green readiness state.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.