> 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/drilldowntree/configuration/formatting/label-configuration.md).

# Label configuration

Open the **Labels** pane (icon tooltip "Labels and tooltips") to style the text in your DrillDownTree and to rename the "Other" node.

<figure><img src="https://3696064508-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffen81laUQFBf286HYARr%2Fuploads%2Fgit-blob-0527a479965d37d27027983cbb967c8fbd759376%2FDDT_Labels.png?alt=media" alt="The Labels pane" width="495"><figcaption></figcaption></figure>

| Setting                    | Range | Default        | Description                                                                                                                                                                             |
| -------------------------- | ----- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Heading color**          | Color | Black          | The color of the headers above each level. A header shows the dimension of that level and the member you selected in it. The inactive tabs of the measure switcher also use this color. |
| **Label color**            | Color | Black          | The color of the node labels (the dimension members).                                                                                                                                   |
| **Measure color**          | Color | Grey (#666666) | The color of the measure value shown with each node.                                                                                                                                    |
| **Label font size (pt)**   | 5–18  | 9              | The font size of the node labels.                                                                                                                                                       |
| **Measure font size (pt)** | 5–18  | 8              | The font size of the measure values.                                                                                                                                                    |
| **Alias for 'Other' node** | Text  | Other          | The name of the node that groups the members that don't fit in a level. Use your own wording, for example "Remaining products".                                                         |

To change how the measure values themselves are formatted (thousands, decimals, percentages, prefix and suffix), use [Measure formatting](https://docs.infotopics.com/drilldowntree/configuration/customize-measures/measure-formatting.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.infotopics.com/drilldowntree/configuration/formatting/label-configuration.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.
