> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-hide-labels.md).

# How do I hide labels on my map?

Kumu automatically shows the label of your element or connections on your map. If you prefer to take them out, you'll have to add a bit of code to your Advanced Editor.

## Hide element labels

To hide the element labels in your map, add the following code to your Advanced Editor:

```scss
element {
  label-visibility: hidden; 
}
```

To only change the *position* of element labels, go to [this guide](/frequently-asked-questions/how-do-i-change-element-text-position.md).

## Hide connection labels

To hide the connection labels in your map, add the following code to your Advanced Editor:

```scss
connection {
  label-visibility: hidden; 
}
```

{% hint style="info" %}
If you'd like to refine which elements or connections to show labels for and which not, please visit our [Selectors guide](/guides/selectors.md) to change the selector to something more precise.
{% endhint %}


---

# 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.kumu.io/frequently-asked-questions/how-do-i-hide-labels.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.