> For the complete documentation index, see [llms.txt](https://docs.chat.ngo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chat.ngo/reporting/reports.md).
# Reports
### **How to Access Reports**
Reports can be accessed in two ways:
1. **From the Workspace Menu**:
* Click on your workspace name in the top navigation bar.
* Select **Reports** from the dropdown menu.
2. **From the Side Menu**:
* Click the **More** icon in the left-hand menu (represented by three dots).
* Select **Reports** from the options.
### **Key Metrics on the Reports Page**
Once you have accessed the Reports page, you will see the following metrics:
1. **Total Number of Messages**: This metric shows the total count of all messages sent within your workspace. It gives you an overview of the communication activity in your workspace.
2. **Total Number of Chats**: This section displays the total number of active chats, providing insight into how much collaboration is happening across your teams and projects.
3. **Active Users**: A bar graph illustrates the number of unique active users over time. This is a useful tool for tracking engagement and seeing when users are most active.
4. **User Engagement**: In this table, you can see each user listed by name, along with their number of chats and messages. This helps assess the level of contribution from each member of your team.
{% hint style="info" %}
Active users are those who have sent at least 1 message in the selected time range.
{% endhint %}
This basic reporting setup is designed to give you a quick glance at user activity and engagement in your workspace, with more detailed and advanced reports coming soon.
---
# 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.chat.ngo/reporting/reports.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.
