> 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-mobile-device.md).

# Creating a new Mobile Device

Perform the following procedure to create a new Mobile Device:

**Note:** The number of Mobile Devices that can be created is limited to the number specified in your site license.

1. Click the **Mobile Devices** tab, and then the **New Mobile Device** button.

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

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

   **Note:** The text in the lower part of the pop-up informs the user that an Enrolment Code will be generated when the Mobile Device is created, on the first save.
2. If you want to replace the default name the system has given the Mobile Device, 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 Mobile Device Configuration pop-up closes.

   There are three tabs, (i.e. **General**, **Action Plans/Alarm Instructions** and **History/Notes** ). The **General** tab displays by default, providing the ability to configure settings for this Mobile Device.

   **Note:** If you require the same system settings to apply to ALL Mobile Devices, refer to [Configuring settings for all Mobile Devices](https://github.com/GGLSecDev/gitbook-spaces-external/tree/main/gallagher-knowledge-base/user-guides/cc-c/en/9.60/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/configuring-global-settings-for-all-mobile-devices/README.md) for further detail.
6. Tick the **Allow connection via the Gallagher API gateway** checkbox if the site has configured the API Gateway and this device is allowed to connect via the API Gateway.

   Before using this feature you need to create a Command Centre Cloud item. For the procedure, refer to the **Connecting to the Cloud** topic in the "Services and Workstations" chapter of the *Configuration Client online help*.
7. Click the appropriate radio button to specify whether or not the Mobile Client application should lock and require user re-authentication after a period of inactivity.

   (Default = Auto-lock after 5 minutes of inactivity. Range = 1 - 59 minutes)
8. Controlling which devices get access to the mobile reader functions is done per device, not per operator, and is controlled by a "Mobile Access Readers" license entry limiting the number of devices.

   Tick the **Enable Mobile Access Reader** checkbox if you want this device to have access to these features.

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

   **Notes:**

   * The indicator below the checkbox states the number of used and remaining licenses on-site, (e.g. 2 of 15 licenses allocated).
   * Once a license has been assigned to a device, the Access Reader icon displays in the main menu of the Mobile Client. In the example below, Mobile Device 2 does NOT have a license assigned to it.

     ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2cdee33c2c8095c4d9c55084f672fcd41ff9b316%2Fmobileclient_accessreadericon.png?alt=media)
9. Controlling which devices can use the Mobile Evacuation feature is done per device, not per operator, and is controlled by a "Mobile Evacuation Devices" license entry limiting the number of devices.

   Tick the **Enable Mobile Evacuation** checkbox if you want this device to be able to use this feature.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4074062a54d0599836f4b2636ea3baae986ab0bc%2Fmobileclient_enableevacuation.png?alt=media)
10. The **Action Plans/Alarm Instructions** tab lists all the Event Groups available for Mobile Devices, and allows you to assign Action Plans and/or Alarm Instructions to them.

    Refer to [Event Action Plans and Alarm Instructions for a Mobile Device](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/event-action-plans-and-alarm-instructions-for-a-mobile-device.md) for further detail.
11. Click the **Save** button.

    A new Mobile Device has been created, and a Device Enrolment Code pop-up displays.

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

    The Enrolment Code needs to be entered on the device, before that device can be used to log on to Command Centre.

    <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b69dccb0017093f37b1b49d332a91f054e52a921%2Fmobileclient_enrolmentscreen.png?alt=media" alt="" width="375">

    **Note:** Enrolment Codes can only be used once and they expire after 24 hours. In case an Enrolment Code does expire before a Mobile Client tries to connect to Command Centre, a new Enrolment Code can be generated. See [Generating new Enrolment Codes](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/generating-new-enrolment-codes.md) for the procedure.

### Hints

{% hint style="info" %}
**Editing and Deleting Mobile Devices**

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 Mobile Devices.

**Note:** Deleting a Mobile Device will clear notification tokens, so that the Mobile Device will no longer receive [Mobile Notifications](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-notifications.md).
{% endhint %}

{% hint style="info" %}
**Duplicating Mobile Devices**

Operators privileged to create mobile devices can also duplicate mobile devices, which makes the task of setting up multiple mobile devices 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-mobile-device.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.
