> 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-change-the-order-of-control-options.md).

# How do I hide control options or change their order?

### Hide control options

After you add a [control](/guides/controls.md) to your map, you might need to rearrange the order of buttons or dropdown options in that control. The best way to accomplish this is to use the `only` option in your control in the Advanced Editor.

Normally, the `only` option is used to restrict the available options in your control. Imagine we have a "Sector" field with the following values:

* Finance
* Agriculture
* Healthcare
* Education

If we only want "Finance" and "Agriculture" to appear in our control, we could use the `only` option to do that:

```scss
@controls {
  top {
    filter {
      target: element;
      by: "Sector";

      // Restrict our filter options from many sectors down to just two:
      only: "Finance", "Agriculture";
    }
  }
}
```

{% hint style="success" %}
If you only wish to exclude a few values from a large list of options, it might actually be shorter to use the `except:` property for the options you *don't* wish to see, instead of listing out *all* the options you *do* wish to see: <br>

```
@controls {
  top {
    filter {
      target: element;
      by: "tags";
      as: dropdown;
      except: Academia, AI;
      multiple: true; 
      default: show-all;
    }
  }
}
```

{% endhint %}

#### Change the order of control options

When you pass options to the `only` property, Kumu will list the control options on the map in the exact order you specified.

In our example above, imagine we want the order of our options to be "Finance", "Education", "Healthcare", and finally "Agriculture". To accomplish that, we can pass that list to the `only` option:

```scss
@controls {
  top {
    filter {
      target: element;
      by: "Sector";

      // Allow all our possible options to show up on the map,
      // but make sure they are in this specific order:
      only: "Finance", "Education", "Healthcare", "Agriculture";
    }
  }
}
```


---

# 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-change-the-order-of-control-options.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.