> ## Documentation Index
> Fetch the complete documentation index at: https://developers.techwolf.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Usage Reports
# Usage Reports
The Analyst Agent keeps a query-level record of how your organization uses it,
and lets your administrators download that record as CSV for any period. Use it
to monitor adoption, review what the agent is being asked, and account for
credit consumption.
Reports cover **every surface**: questions asked in the TechWolf Console and
questions asked through Microsoft 365 Copilot appear in the same files.
# Who can see reports
Reports are available to users with the **Reports Viewer** role under
**Analyst Agent**, assigned per user in the Console's User Management exactly
like agent access itself. Any user who can manage users in your Console can
assign it; see [User Management](./user-management).
**Reports Viewer** includes everything **Viewer** gives, plus the reports,
so it replaces **Viewer** rather than sitting next to it. Users with plain
**Viewer** keep using the agent but do not see the reports.
Users with **Reports Viewer** open the menu in the top right of the agent and
select **Usage Reports**.
There is no reports view inside the Microsoft 365 Copilot experience.
Copilot usage is included in the reports, but the reports themselves are
downloaded from the TechWolf Console.
# The reports page
Pick a **From** and **To** date. The summary line gives the number of queries
and the number of distinct people in that period, and the graph breaks both down
by week (Monday to Sunday, UTC) so you can see the trend before downloading
anything.
The page offers two reports over the chosen period.
## Usage report
One row per query: who asked, when, from which surface, and the credits it drew.
Queries that drew no credits are included as zero-credit rows, so this is the
complete record of activity rather than only the chargeable part.
| Column | What it holds |
| ----------------- | ------------------------------------------------------------------------------------ |
| `timestamp` | When the answer was returned, in UTC |
| `user_id` | The person who asked. Stable and consistent across surfaces, so one person is one id |
| `conversation_id` | The chat the query belongs to, so related queries can be grouped |
| `query_id` | The query itself, and the join key to the question-answer report |
| `source` | Where it was asked: `console` or `copilot` |
| `size` | How much work the query took: `none`, `small`, `medium` or `large` |
| `credits` | Credits the query drew, `0` in the `none` band. See [Credits](./credits) |
## Question-answer report
Each question with the final answer it received. Nothing else: no reasoning
steps, no tool activity, no intermediate output. It carries the same first five
columns as the usage report, so the two files join on `query_id`.
| Column | What it holds |
| ----------------- | ------------------------------------ |
| `timestamp` | When the answer was returned, in UTC |
| `user_id` | The person who asked |
| `conversation_id` | The chat the query belongs to |
| `query_id` | The join key to the usage report |
| `source` | `console` or `copilot` |
| `question` | The question as the user asked it |
| `answer` | The final answer the user received |
# What the reports contain
* **People are identified by a stable id, not by name or email address.** The
same person carries the same `user_id` in both reports and on every surface,
so you can count distinct users and follow one user's activity without the
files carrying anyone's identity.
* **TechWolf accounts are excluded.** Sessions run by TechWolf staff assisting
your team do not appear, and never draw on your credits.
* **Answered queries only.** A question the agent asked you back, before it
started any work, is not a query.
If you see anything in the documentation that is not correct, does not match
your experience or requires further clarification, please reach out to us at
[support@techwolf.ai](mailto:support@techwolf.ai).