> 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-elements-without-connections.md).

# How do I hide elements without connections?

Elements without any connections are called "orphans" and might sometimes distract from your main map.

To hide orphans in your map, use the `ignore-orphans` property in the `@settings` block to automatically filter out any elements that have no connections. Possible values for this property are `true` or `false`.

```scss
@settings {
    ignore-orphans: true;
}
```

## Dynamic hiding of orphans

**With a control**\
You might not *always* want to hide the orphans in your map. To add a handy control to your map that toggles orphans on and off whenever needed, add this code to your advanced editor:

```scss
@controls {
 top {
 filter {
  target: :orphan;
  as: label;

  option {
    selector: *;
    default: true;
    label: "Hide elements without connections";
   }
  }
 }
}
```

To adjust the location or aesthetic of your control, visit the [Controls guide](/guides/controls.md).

**Automatic**\
If you want the hiding of orphans to be a bit more automatic, simply add `filter-ignore-orphans: true;` to your `@settings {` block and Kumu will automatically ignore orphans when you activate your filter. It'll look like this: 

```
@settings {
filter-ignore-orphans: true;
}
```

{% hint style="warning" %}
*One caveat: this "automatic" way to ignore orphans only works on elements that were never connected in the first place. Any elements that do have connections when the filter isn’t activated will not be filtered out.*
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kumu.io/frequently-asked-questions/how-do-i-hide-elements-without-connections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.