Usage statement

Admin → Usage is the monthly statement: one page that rolls up everything the workspace consumed in a given month, for invoicing and for keeping an eye on spend. Pick a month at the top; Export CSV gives you the same figures as a file. It’s an admin-only view.

It is the only usage screen in the workspace: the older per-screen views (AI usage, Storage, API usage) were folded into it, and the money behind them lives with ddx, not in the workspace.

What’s on it

• AI credits — never a currency figure. If your plan sets a monthly ceiling, this is the month’s AI usage as a percentage of it, with a bar that goes green → amber (at the warn threshold) → red (at the ceiling). If no plan ceiling is set, it is today’s usage as a percentage of the default daily allowance, which is what actually pauses AI work when nothing else is configured. The daily allowance still applies alongside a plan ceiling, so a workspace on a plan can be paused for the rest of the day while its month is well under the ceiling; the notice says which one is holding. A closed month shows its usage against the plan, and nothing about today. Each project shows its share of the month’s usage and, when a plan ceiling exists, its own percentage of the credits.
• Storage — the latest sweep’s size, the month’s peak, and your allowance if the plan sets one, with a per-project table beneath: each project’s ingest attachments and filed documents (every stored revision counts, and files pending deletion still occupy storage until erased). It is the logical footprint, so it will not add up exactly to the physical figure.
• Filing downloads — how much was downloaded from Files (audited downloads; the underlying R2 egress itself is free — this is a usage signal, not a bill).
• External participants — how many outside organisations and active delivery engagements the workspace has.
• Filing volume — live documents, versions added this month, transmittals issued.
• LLM spend by project — the same total, broken down per project.

Plan lines and ceilings

Plan lines — the LLM ceiling, warn threshold and storage allowance — are set per contract by ddx. They aren’t editable in the workspace: a tenant can’t raise its own plan. That’s by design.

The monthly LLM ceiling is an enforced limit, not just a display:

• Below the warn threshold, everything runs normally.
• At the warn threshold, the bar turns amber — a heads-up, no effect on service.
• At the ceiling, the workspace stops spending on LLMs for the rest of the month: ingestion holds (communications queue rather than being classified), task translations pause (texts show as written), the task dialogs’ suggestions go quiet (the close gate’s box comes clear and a pin’s item takes its instruction’s first sentence) and chat refuses with a clear message. All of it resumes when the month rolls over, or when ddx raises the plan.

This sits on top of the existing per-day guard — the day ceiling still applies within the month.

Note

Holding is not losing. Ingestion that’s held while at the ceiling isn’t dropped — it’s queued, and processes once headroom returns.