> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/whats-new/october-2024/saved-views-on-dashboard.md).
# Saved Views on Dashboard
Saving a View on Coverage Dashboard
SeaLights is excited to introduce a new feature that empowers you to customize your Coverage Dashboard experience: Saved Views. Now you can create and save preferred views of the Coverage Dashboard, tailored to your specific analysis needs.
## **Key Benefits**
* **Tailored Insights:** Create custom views focused on the data that matters most to you.
* **Increased Efficiency:** Quickly access your preferred view with a single click.
* **Enhanced Collaboration:** Share saved views with your team to foster collaboration and knowledge sharing.
## **How it Works**
* **Set Filters:** Select your desired filters using the Dashboard Coverage Filter popup.
* **Create and Save Your View:** (requires Admins or DevOps permissions) Create a new view, assign a descriptive name and save it for future use.
* **Share with Your Team:** Saved views created by Admins or DevOps are available to all team members by the Saved Views dropdown.
* **Manage Saved Views:** Access and manage your saved views. Note that only the creator of a saved view can delete it.
***
By leveraging saved views, you can streamline your analysis process and gain deeper insights into your coverage data.
---
# 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.sealights.io/knowledgebase/whats-new/october-2024/saved-views-on-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.
