> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/textual-monitoring/usage-report.md).
# Downloading a usage report
{% hint style="info" %}
**Required global permission:** View usage metrics
Not available on Textual Cloud.
{% endhint %}
The usage report is a .csv file that summarizes the Textual processing for an organization.
## Information in the usage report
For each action, the usage report includes the following information:
Example usage report
* Type of action
* Number of words consumed
* Total size of the file
* Name of the related dataset
* List of tags that are assigned to the dataset
* Job identifier that is associated with the action
* The identifier of the user who performed the action
* The identifier of the organization that the user belongs to
* The timestamp for the action
## Downloading the report
To download the report, on the **System Settings** page, click **Download Usage Report**.
The report is downloaded as **usage\_report.csv**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tonic.ai/textual/textual-install-administer/textual-monitoring/usage-report.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
