> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/cross-platform-features/list-of-cross-platform-features/saved-views.md).

# Saved Views

A Finout view is how you can save and name a set of filters and the applied group by, allowing you to easily return to view the required data and share this with your team. In addition, the time aggregation (daily, weekly, monthly) and period of the query are also saved as part of the view.

The filters can be applied using out-of-the-box resources such as Azure, GCP, AWS, Datadog, GCP, Global, Kubernetes, Snowflake, or Databricks, as well as custom views using virtual tags to view the costs associated with logical categories. You can create as many views as required, and these are shared automatically with all users in your account.

* [Custom Views](/cross-platform-features/list-of-cross-platform-features/saved-views/custom-views.md)
* [Predefined Views](/cross-platform-features/list-of-cross-platform-features/saved-views/predefined-views.md)

{% hint style="info" %}
**Note**: A view can be applied to a cost report or as a Dashboard widget.
{% endhint %}


---

# 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.finout.io/cross-platform-features/list-of-cross-platform-features/saved-views.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.