Docs · Guides

Workspace usage

The Usage tab (/workspace/usage) shows how much of your organization’s plan you have actually consumed, right now, in one place.

Who can see it

Any authenticated member of the active organization can open the page — there is no role gate. The lowest role that can read the organization reads exactly the same figures an owner does.

The three meters

The page shows exactly three meters, each read from its own live, authoritative source — never from a lagging internal copy:

MeterWhat it measures
API results this periodCounted results submitted against your organization’s current billing period
StorageTotal bytes stored across every attachment surface (test results, defects, comments, and more)
SeatsMembers and pending invitations counted against your seat limit

Each meter shows the used figure beside its effective ceiling — the same ceiling your organization’s entitlements resolve to everywhere else in the product, including any per-organization override. There is no fourth meter on this page: projects, rate limits, and retention are not shown here.

Because every figure is read live, at the moment you open the page, raising a limit — for example a seat-limit override applied by staff — is reflected the next time you read this page. Nothing needs to be redeployed.

When a ceiling is unlimited

If your organization’s effective ceiling for a meter is unlimited, that meter shows the used count and states plainly that the ceiling is unlimited — it never shows a percentage, a remaining amount, or a progress bar for that meter. There is no 0% or 100% to misread; the unlimited state is its own explicit presentation, not a percentage computed against a very large number.

Live figures, not a staff-facing snapshot

The numbers on this page always come from the same live endpoints an integrator would call directly — the storage-usage, API-result-usage, and seat-usage endpoints described in the API reference. Staff tooling separately keeps a periodically refreshed copy of some of these figures for platform-wide monitoring; that copy is never what this page shows you, so what you see here is always current.