> 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 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.