Usage is the organization-wide view of what you are consuming against what you bought. It belongs in Administration because it answers a question about the whole organization rather than one builder's work.
Two meters
The price list measures two things: breadth — how many people and customer-facing surfaces the organization has — and work — how much machine work it does in a month.
- Users — every employee with a membership, at any access level, including people invited but not yet signed in.
- Governance seats — the people who can own governed material.
- Customer-facing surfaces — each chatbot with a published widget and each search agent with a live publishable key counts once, against what the plan includes.
- Work capacity — this month's answers, web searches, pages read, pages re-synced, speech and images, shown as a percentage of what the plan includes. You never see a token count: the page says how much is used, where the month is heading at the current pace, and what the rest is enough for, such as about 1 200 answers.
Work capacity and surfaces are shown and warned at 80 % and 100 %, but nothing is stopped or charged for them yet. Going over an allowance on any meter is not invoiced as overage — it is a conversation about the arrangement, not a surprise on a bill.
What does not count
Loading Knowledge for the first time does not draw work capacity; re-syncing it does. Neither does the work Tindre does on its own: conversation analysis, knowledge gaps and coverage, and automatic titles. Knowledge itself is fair use — how much the organization stores is not metered against it.
Read it beside the evidence
Usage counts allowances. It is not an analytics product: to understand what people are actually asking and how well it is answered, use an Agent's conversations and measurements instead.