> 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/custom-views.md).
# Custom Views
## Creating Views
### Create a Custom View
1. Apply the required **Filters** on the MegaBill page.
2. Select the required **Group By** option.
3. Select whether the data should be calculated as Daily, Weekly, or Monthly, and select the period of the report.
4. Click **Save**.
5. Enter a view **name**.
6. If this is a new view, select **Save as a new view** and then click **Save View**. If this is an existing view you are modifying, ensure that the **Save as the new view** is not selected.
### Creating a new view based on an existing view
1. In **Total Cost**, select the required view from the dropdown.
2. Update the view options as required:
1. Apply the required Filters.
2. Select the required **Group By** option.
3. Select whether the data should be calculated as Daily, Weekly, or Monthly.
4. Select the period of the report.
3. Click **Save**.
4. Enter a **View name**.
5. Select **Save** as new view.
6. Click **Save View**.
or-
7. In **Total Cost**, select the views dropdown.
8. Click copy Icon (double square). The view is copied.
9. Edit the view as required.
## Using and Managing Views
### Using a view in a widget
1. In the **Dashboards** , click **Create Dashboard**.
2. Click **Add Widget**.
3. Select a widget or template.
4. In the **Load from saved** view dropdown, select the required view.
5. Configure the other widget options and click **Save and return**.
### Change a view name
1. In **Total Cost**, select the views dropdown.
2. Click the **Pencil icon**.
3. Enter the **View name**.
4. Click **Save View**.
### Deleting a view
1. In **Total Cost**, select the views dropdown.
2. Click the **trashcan icon**.
3. Click **Delete View**. This deletes the view for all users in the account.
### Updating an existing view
1. In **Total Cost** , select the required view from the dropdown.
2. Update the view options as required:
1. Apply the required Filters.
2. Select the required **Group By** option.
3. Select whether the data should be calculated as Daily, Weekly, or Monthly.
4. Select the period of the report.
3. Click **Save**.
4. Click **Save View**.
## View Examples
**Example 1:**
This report details the costs associated with two specific Amazon EKS clusters in your Amazon Web Services account grouped by Kubernetes namespaces. The view shows the daily costs for the past 30 days.
**Example 2:**
This report details the costs associated with AWS grouped by AWS Sub-Service. The view shows the daily costs for the current month.
Still need help? Please feel free to reach out to our team at .
---
# 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/custom-views.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.
