> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/rentals/rental-details.md).
# Rental Details
Rental details can be accessed through the dashboard by clicking on Active Rentals, on the Rentals tab of a specific [hardware](/admin-site/modes.md), or on the Rentals section of a particular [user](/admin-site/users/user-details.md). When you view the Rental details screen, you'll see:
* A map of where the rental took place
* For systems that support tracking, you'll get a view of where the user has taken the hardware (represented by a red line on the map).
* If you have enabled the [`Enable User Device GPS Usage`](/admin-site/settings/rentals.md) setting, you will also have access to the user's GPS data, which is represented by a yellow line on the map. This feature is particularly useful for hardware that does not support GPS.
* The hardware number.
* The user associated with the rental.
* Start and end point of rental.
* Duration of the rental (start and end timestamps).
* User rating for the rental (between 1 and 5 stars).
* Total Distance travelled (for systems that support tracking).
---
# 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://documentation.movatic.co/admin-site/rentals/rental-details.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.
