> 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-doors-to-a-panel.md).

# Adding Doors to a Panel (Monitor Site Viewer Navigation Panel)

Specific doors are associated with a Panel, and are the conditions that control when the associated Panel name will flash (to attract the user's attention) in the Viewer Navigation Panel.

1. Ensure the Panel you want to associate Doors to is selected, and click the **Select Door(s)** button.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ab0292e2aa4d5d35fdaa0e8639770bdd448bd9e3%2Fselectdoorstomonitorpopup.png?alt=media)

   **Note:** The Door monitored must be a local Door. Identifying a Cardholder who last badged at a remote Door is not possible.
2. If necessary, search for the Door(s) you want to add to the Panel by entering search criteria in the **Search** field and/or refining the Division filter.

   The grid becomes populated with Doors that match the search criteria.
3. Click the checkbox next to each Door name you want to include, or click the **Select All** button if you want to include all Doors.
4. Click the **Add Selection** button.

   The pop-up closes and each of the Door(s) that was selected individually appears in the grid on the right when that Panel is selected in the **Panels** list.


---

# 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-doors-to-a-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.
