> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/admin/admin-page/watch-containers.md).
# Watch containers
Insight UI - Consolidated Admin
The **Containers** accordion on a watch's edit panel enables you to include this watch in one or more containers. Logos are shown if a logo has been added to the container.
### Available containers - left panel
**Filter** — Enter text to select containers whose name or description contain that string (case is ignored).
* **+** Click to add this watch to the container.
* **−** Indicates this watch is already included in the container; click to remove it.
### Included in these containers - right panel
See a list of all containers in which this watch is included. Use the **−** button to remove this watch from the container.
{% hint style="warning" icon="eyes" %}
Note: You will not see a container listed if:
* The container is above your user folder/location in the tree.
* The container is set to Visibility: Internal and you are a user in a customer folder.
* The container is enabled for maintenance and you do not have the Manage maintenance permission.
{% endhint %}
{% hint style="info" %}
One save stores details for all accordions.
{% 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://help.highlight.net/admin/admin-page/watch-containers.md?ask=&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.
