> 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/using-command-centre/licensable-features/tag-board-feature/operator-selected-access-zones.md).

# Operator selected Access Zones

If a Tag Board Tile has been configured to allow operators to choose the Access Zones to be monitored, there will be additional options for:

* Dragging and dropping Access Zones onto the tile from a Status or Site Plan Tile.

  **Note:** When dragging from a Site Plan Tile, either the icon or the area associated with the Access Zone item can be dragged across. Monitoring of an Access Zone begins as soon as it is dragged onto the Tag Board Tile.
* Adding and removing Access Zones using the **Change Zones** button, as follows:

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

1. Click the **Change Zones** button.

   The Tag Board Access Zones pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-34b766a9f4127b40edc858873e8a4ca36e3199da%2Ftagboardaccesszones_popup.png?alt=media)
2. What action do you want to take?

   <table><thead><tr><th width="180">To...</th><th>then...</th></tr></thead><tbody><tr><td>add Access Zone(s),</td><td><ol><li>Click the <strong>Add Access Zones</strong> button.<br>A browse tool displays.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-0a7dcafbff44e382e22b3f078cb869deb8ee6eb2%2Fselectaccesszonepopup.png?alt=media" alt=""><br></li><li>If necessary, search for the Access Zone(s) you want by entering characters in the <strong>Search</strong> field and/or refining the search mode and filters.<br>The grid becomes populated with Access Zones that match the search criteria.</li><li>Check the Access Zone(s) you want to be monitored, and click the <strong>Add Selection</strong> button.<br>The browse tool closes, and the selected Access Zone(s) appear on the Tag Board Access Zones pop-up.</li></ol></td></tr><tr><td>remove Access Zone(s),</td><td>uncheck the checkbox beside the Access Zone(s) you want to remove.<br><br><strong>Note:</strong> If you want to remove all the Access Zones currently selected, click the <strong>Deselect All</strong> button.</td></tr></tbody></table>
3. Click the **OK** button.

   The Tag Board Access Zones pop-up closes. The first time the tile is displayed for an operator it will be empty. Subsequently, operator preferences will determine the Zones being monitored from this tile.


---

# 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/using-command-centre/licensable-features/tag-board-feature/operator-selected-access-zones.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.
