> 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/configuring-licensable-features/mobile-client-configuration/creating-a-new-monitored-area.md).

# Creating a new Monitored Area

Mobile Evacuation Monitored Areas are created as a collection of one or more Access Zones.

Perform the following procedure to create a new Monitored Area:

1. Click the **Mobile Evacuation** tab, and then the **New Monitored Area** button.

   The new Mobile Evacuation Monitored Area is added to the Viewer Navigation Panel, and the Monitored Area Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b4659fbf799cbc93683eca5d914618a1c6ad7933%2Fmonitoredareaconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Mobile Evacuation Monitored Area, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical Description (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Mobile Device to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.
5. Click the **Close** button.

   The Monitored Area Configuration pop-up closes.

   There are two tabs, (i.e. **General** and **History/Notes** ). The **General** tab displays by default, providing the ability to configure Access Zones for this Monitored Area.
6. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7de6b50a01686c98a72fc192de7e38cc162e1efb%2Fmobiletagboard_addaz.png?alt=media) **Add Access Zone** button.

   The Add Access Zones browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9a699b51795e6abfce3313b2493013089e013ea3%2Faddaccesszones_popup.png?alt=media)
7. If necessary, search for the Access Zone(s) you want by entering characters in the Search field and/or refining the search mode and filters.

   The grid becomes populated with Access Zone(s) that match the search criteria.
8. Click the checkbox next to each Access Zone name you want to include, or click the **Select All** button if you want to include all Access Zones.

   **Note:** An Access Zone can only be added to the same Monitored Area once, but can be added to multiple Monitored Areas.
9. Click the **Add Selection** button.

   The browse tool closes and each of the selected Access Zone(s) appear in the **Access Zones** grid.

   **Note:** To remove an Access Zone, select (highlight) it you the zone you want to remove and click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-0e6d198e37d414a2c22d5a9c6ad800dd05528792%2Fmobiletagboard_removeaz.png?alt=media) **Remove Access Zone** button.
10. If you want this Mobile Evacuation Monitored Area to ignore location information more than a specified number of hours old, check the **Ignore location information older than** checkbox, and (if necessary) change the default figure of '24' to the number of hours required.

    The effect of this will be to exclude cardholders from the Monitored Area when the last (most recent) location update was older than X.
11. If you want to record any note(s) about the Monitored Area, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
12. Click the **Save** button.

    A new Mobile Evacuation Monitored Area has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Mobile Evacuation Monitored Areas**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Monitored Areas.
{% endhint %}

{% hint style="info" %}
**Duplicating Mobile Evacuation Monitored Areas**

Operators privileged to create Monitored Areas can also duplicate Monitored Areas, which makes the task of setting up multiple Monitored Areas that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% 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.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/creating-a-new-monitored-area.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.
