> For the complete documentation index, see [llms.txt](https://docs.xviz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xviz.com/performance-management/configuring-the-chart-structure/invisible-group.md).

# Invisible Group

To hide a group within a structured layout, we can set its color value to **-1**, effectively making the group invisible. This approach ensures a proper structure with correct alignment.

**Use Case Example:**

Suppose we want to group only the **Tech Team** while keeping other teams ungrouped. Without invisible groups, the alignment becomes inconsistent, as shown in the Image below:&#x20;

<figure><img src="/files/GsrJDNw4ck7gOzpl5jiV" alt="" width="375"><figcaption><p>Image 1: Structure without Invisible Group</p></figcaption></figure>

By applying invisible groups to the other teams, we can hide them while maintaining a well-structured and properly aligned layout as shown in the image below:

<figure><img src="/files/lujBNcmQuFlterDi1Cf7" alt="" width="375"><figcaption><p>Image 2: Structure with Invisible Group</p></figcaption></figure>


---

# 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.xviz.com/performance-management/configuring-the-chart-structure/invisible-group.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.
