> For the complete documentation index, see [llms.txt](https://docs.tabnine.com/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tabnine.com/main/administering-tabnine/managing-your-team/reporting/usage-per-user-page.md).
# Usage Per User page
The Usage Per User page provides a user-level breakdown of Tabnine adoption and activity across the organization.
The **Usage Per User** page provides a user-level breakdown of Tabnine adoption and activity across the organization.
At the top of the page, administrators can filter the data by **team** and **time frame**. In the screenshot, the page is showing **all teams** for the **last 30 days**. The search field on the right can be used to locate a specific user by email address.
Each row represents an individual user. The table shows the user, their team, then the number of several items (Accepted Completions, Chat Interactions, Agent Interactions, Chat Lines of Code, and Agent Lines of Code), Automation Factor, and User Status.
{% hint style="info" %}
For full explanations of these items, see the [Reports Glossary](/main/administering-tabnine/managing-your-team/reporting/reports-glossary.md).
{% endhint %}
{% hint style="info" %}
As of [v6.4.0](https://docs.tabnine.com/main/administering-tabnine/managing-your-team/reporting/pages/risy3bTOlfBfgFRRXK8K#v6.4.0), Agent Usage includes all Tabnine Agent activity across both the IDE Agent and CLI Agent
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tabnine.com/main/administering-tabnine/managing-your-team/reporting/usage-per-user-page.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 `automate deployments from our CI pipeline` 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.
