> 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-the-settings-button.md).

# How do I hide the settings button?

The Settings button on the right side of your map allows you to access the Basic Editor and the Advanced Editor to adjust the visualization and structure of your map. 

When you're building a map, it's usually helpful to have the Settings button close by, so you can access these [view editors](/overview/user-interfaces/view-editors.md). But, when you're showing a map to your audience, you might sometimes want to hide it, so that they don't get confused by all of Kumu's features and options.

{% hint style="info" %}
Don't worry! Viewers of your map aren't actually able to *save* the changes made to your map. So if you decide to keep the Settings button in place, nothing will happen to it. 
{% endhint %}

To hide the settings button, you can edit the [built-in controls](/guides/controls.md#built-in-controls). Specifically, you can copy/paste this snippet of code into your [Advanced Editor](/overview/user-interfaces/view-editors.md#advanced-editor), right at the top:

```scss
@controls {
  top-right {
    zoom-toolbar {}
    focus-toolbar {}
  }
}
```

Then, click **SAVE** at the bottom of the editor to save your changes.

This snippet of code will instruct Kumu to show only the zoom toolbar and—when an item is selected on the map—the [focus](/guides/focus.md) toolbar. The settings button will no longer appear.

{% hint style="success" %}
Even if the settings button is hidden, it's always possible to open the Settings panel by pressing `T` on your keyboard.
{% 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-the-settings-button.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.