> 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/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).

# Cameras tab

All site items include a **Cameras** tab in their Properties window. This tab allows you to assign DVR Cameras to a site item, so that when an event occurs at the item, the **Camera** tile in Command Centre Client will display footage for the camera associated with it.

**Note:** The procedure and example screen shot below is for an Access Zone, however the procedure is still the same for all site items.

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

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens.
2. Select those DVR Camera(s) appropriate for this Access Zone.

   Drag and drop them into the grid on the **Cameras** tab.

   The **Camera** tile in Command Centre Client can be configured to display live feed from one of the cameras listed in this grid.

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

   **Note:** The **up** and **down** arrows to the side can be used to change the order of the DVR Cameras if required.

   The order you sort the cameras here will be their “position in list” when you choose to Live feed from Event Source Camera and specify the number of the camera that the feed will be taken from in Command Centre Client.


---

# 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/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.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.
