> 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/network-diagram-2.0/color.md).

# Color

Click the ‘Use new color formatting’ checkbox to use the new color options.

<figure><img src="https://1632500807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ARtwElTSzdwWxw4t1pi%2Fuploads%2FWCK0pQN3zj9JgRl9oMaG%2Fimage.png?alt=media&amp;token=3e6ed322-4f94-45b4-a49d-16554e38eb10" alt="" width="375"><figcaption><p>Network diagram configuration panel -> Color</p></figcaption></figure>

#### Background color

Use the circle to open the color palette to change the background color of your Network Diagram. Use this to best match your dashboard color style.

#### Color mode

Choose between Color Nodes or Color Nodes and Links. Coloring just the nodes will leave the links grey.

#### Mark colors

Use the circles to open the color palette to change the colors of the marks. The order they are in will be the order of your levels.

#### Select colors for dimensions: (New color formatting only)

Click on the color palette that’s alongside your chosen dimensions to choose their color. The new coloring format will improve your ease of use by seeing which dimension is represented by which color.


---

# 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/network-diagram-2.0/color.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.