> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/masterstudy-lms/lms-settings/reports-and-analytics.md).
# Reports & Analytics
Pro Plus Feature
In the Reports & Analytics tab of the plugin settings, you can enable or disable reports for instructors and students. For admin, it will always be accessible. Here is the overview of the tab:
* **Reports for Instructors** - enable to display the advanced [analytics to instructors. ](/masterstudy-lms/lms-analytics/analytics-for-instructors.md)
* **Show payout statistics to instructors** - enable to display of payout statistics for instructors in the [**Revenue tab**](/masterstudy-lms/lms-analytics/analytics-for-instructors/revenue.md).
* **Reports for Students** - enable to show [reports to students.](/masterstudy-lms/lms-analytics/student-reports.md)
* **Email Reports** - a button that redirects to manage[ emails regarding the **Reports & Analytics**](/masterstudy-lms/lms-pro-addons/email-manager/email-templates.md#reports) feature.
Detailed information about the **Reports & Analytics** function of **MasterStudy LMS** can be checked here:
{% content-ref url="/pages/CZwi6DLPWaJ1bQ8p1JOk" %}
[LMS Analytics](/masterstudy-lms/lms-analytics/analytics-for-admin.md)
{% endcontent-ref %}
---
# 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.stylemixthemes.com/masterstudy-lms/lms-settings/reports-and-analytics.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.
