> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/reputation/dashboard.md).
# Dashboard
How to navigate and review your reputation dashboard
When the Reputation feature is enabled in your account, your dashboard will look like this:
But what exactly is this dashboard used for? The dashboard allows you to filter your responses to find specific feedback and respond as needed.
Using the filters at the top of the page, you can filter based on Location, Review Source, Time (when the review was made), and the rating you were given in the review.
The rest of the dashboard can be used to view overall stats for the reviews and feedback you have received, such as the below graphs.
To respond to feedback directly, click on the Reviews section on the left-hand menu below Reputation.
---
# 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.gleantap.com/reputation/dashboard.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.
