> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/analytics+/color-scales.md).

# Color Scales

Learn how to enhance your visuals using Color Scales in Inforiver Analytics+. Whether you're working with **sequential, diverging,** or **custom color schemes**, this guide walks you through every step to make your charts more insightful and visually compelling.

What you'll learn:

* How to access and apply color scales via Conditional Formatting
* Choosing between **Sequential, Qualitative, Diverging,** and **Custom scales**
* Applying formatting to specific chart elements like Data labels, X-axis labels, and Totals
* Exploring advanced options like **Color Blind-friendly** and **Continuous Diverging scales**
* **Reversing scales** and customizing band counts for deeper visual control

{% embed url="<https://vimeo.com/1149145481>" %}


---

# 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://videos.inforiver.com/analytics+/color-scales.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.