> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/ibcs-user-guide/ibcs/scaling-multiple-charts.md).
# Scaling Multiple Charts
#### Configure multiple charts to use the same scaling
When there are many charts on a same page or panel of a dashboard, it is generally advantageous to use the same value axes scaling. This may be necessary not only for the same metric but also across metrics (for example, to represent income and spending).
You may simply accomplish this using the properties editor. A drop down selector for the scaling group may be found in the IBCS section of the properties editor.
Choose a scaling group, and then repeat for all of the charts on the same page that must be in the same group. You can also put some of the charts in one group and some in another (on the same page).
Here’s an example of a page with many charts with distinct metrics that are all scaled by placing all charts in the ‘Group 1’ scaling group.
**Demo video**
---
# 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.vitaracharts.com/ibcs-user-guide/ibcs/scaling-multiple-charts.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.
