> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/configuring-the-viewer-navigation-panel/monitor-site-viewer/adding-a-new-panel.md).

# Adding a new Panel to a Monitor Site Viewer Navigation Panel

1. Click the **New Panel** button.

   A new Panel appears in the **Panels** list with a default name of *'Panel \<number>'*. The number on the end ensures the Panel name is unique, and increments by one each time a new Panel is added.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c7c14daa5577ec5fbd8b9da791b94cc15284ad4e%2Faddnewpanel.png?alt=media)
2. Give the Panel a more meaningful name if required.

   **Notes:**

   * You cannot enter a name which is a duplicate of another Panel for the same Viewer.
   * You can use the up and down arrows to the side to change the order of the Panels, (i.e. select the Panel you want to move and click either the up or down arrow to move it).


---

# 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.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/viewer-configuration-overall-process/configuring-the-viewer-navigation-panel/monitor-site-viewer/adding-a-new-panel.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.
