> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/dashboards/favorite-dashboard.md).

# Favorite Dashboard

The OvalEdge Favorite Dashboard streamlines the user's data experience by offering a dedicated space tailored to their needs. Unlike standard dashboards, it reflects user preferences and requirements.

* **Easy Access & Ownership:** Upon signup, every OvalEdge user receives a Favorites Dashboard regardless of their license. This dashboard is displayed to facilitate access to the user's data.
* **Customization & Functionality:** Users can add and remove reports, such as standard dashboards, to personalize their view. The key advantage lies in its direct association with the user's account, allowing them to curate reports relevant to their role.
* **Enhanced Organization & Security:** The Favorites Dashboard goes beyond report integration. It includes:
  * **Access Control:** Ensures users only include reports with appropriate permissions, safeguarding data security.
  * **Labeling System:** Facilitates easy organization and identification of user reports, boosting usability.

Combining personalization, organization, and security, the OvalEdge Favorites Dashboard becomes essential for users to manage their data effectively.


---

# 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.ovaledge.com/release7.2/dashboards/favorite-dashboard.md?ask=<question>&goal=<user_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.