> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/sankey-diagram/color-formatting/color-nodes.md).
# Color nodes
**Color by (Node)**
The color by settings will let you configure node colors
{% tabs %}
{% tab title="Color by dimension" %}
This will only be available when clicking on ’Color by dimension’. All nodes and links will be colored by dimension. This would be ideal to show the flow from one dimension to the next. When clicking you will be presented with the categories available for you to then change the colors of your dimensions.
{% endtab %}
{% tab title="The same values have the same colorsab" %}
Your Sankey Diagram will display the same color for data points with the same value. This is useful for highlighting exact matches across different categories. When selecting this option, you will see all available dimension members, and can click on each color palette to make edits.
{% endtab %}
{% tab title="All values have unique colors" %}
Each value will have its own unique color. This is ideal if you wish to differentiate between specific or all nodes, for example. When selecting, you will be presented with the available values. Click on each color palette to edit.
{% endtab %}
{% tab title="Color by tag" %}
{% endtab %}
{% endtabs %}
---
# 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.infotopics.com/showmemore/features/sankey-diagram/color-formatting/color-nodes.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.
