> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/browse-purchase-and-manage-classes/admin-transactions-screen.md).
# Admin Transactions Screen
The Admin Transactions Screen of the Browse, Purchase, and Manage Classes Feature Template is a dashboard view of the transactions successfully completed by customers.
The ‘Admin Tractions’ screen is a quick way for administrators to get an overview of the most recent transactions and operates as a dashboard for your business.
Similar to the ‘Admin Manage Clinics’ screen, it comes with a side navigation component set to highlight the “Transactions” menu item.
## New Components
### **Text Components — Various**
These text components display unique and dynamic information from the database. From left to right:
1. A count of all transactions from the Transactions Collection.
2. A count of all transactions in the last 30 days. This is because the text uses a custom filter for “Created Date” is after “30 days ago.”
3. A count of the total number of users who have purchased. This uses a custom filter to search for any users that have a transaction count higher than one.
4. A custom formula to display the percentage of users who have purchased a course out of the total number of Users in the database.
---
# 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://help.adalo.com/feature-templates/browse-purchase-and-manage-classes/admin-transactions-screen.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.
