> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/settings/chart-layouts.md).

# Charts Layouts

Settings category for multi charts application tab

<figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2Fo0p5FiOeS3Qg7SXxt39e%2Fimage.png?alt=media&amp;token=14f08f34-76a3-4f59-9153-32e722c74276" alt="Charts Layouts settings for creating, renaming, and deleting saved chart layouts."><figcaption><p>Charts Layouts settings for creating, renaming, and deleting saved chart layouts.</p></figcaption></figure>

Charts Layouts settings manage saved layouts for the [Multi charts](/features/multi-charts.md) tab.

Use this page when you want to organize chart workspaces without opening each layout in the chart view first.

## Available actions

<table><thead><tr><th width="136.875">Action</th><th>What it does</th></tr></thead><tbody><tr><td>Create</td><td>Adds a new layout that can hold its own chart grid.</td></tr><tr><td>Rename</td><td>Updates the layout name shown in selectors.</td></tr><tr><td>Delete</td><td>Removes the layout and its saved chart arrangement.</td></tr></tbody></table>

Deleting a saved layout also removes the local chart snapshots associated with charts in that layout. Use delete only when you are sure the layout is no longer needed.

For day-to-day layout switching, use the topbar in [Multi charts](/features/multi-charts.md).


---

# 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.proliquid.xyz/settings/chart-layouts.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.