> 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/reporting-overview.md).
# Reporting Overview
The reporting feature in ChatNGO provides workspace admins and managers with insights into how the platform is being used. Reports can help you measure activity, user engagement, and the overall usage of your workspace. This functionality can be essential for understanding how effectively teams are collaborating and communicating, providing data-driven insights for improvement.
### **Benefits of Using Reports**
* **Monitor Team Activity**: Keep track of message volume and the number of active users to ensure everyone is engaged and collaborating efficiently.
* **Assess Workspace Usage**: Gauge the effectiveness of your workspace by tracking the number of chats and messages.
* **Data-Driven Insights**: Gain valuable insights into how different teams or users are interacting, allowing you to optimize workflows and collaboration efforts.
Stay tuned for additional reporting features that will expand the depth of analysis available in future updates.
---
# 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/reporting-overview.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.
