> 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/mobile-devices-global-settings.md).

# Configuring Global Settings for all Mobile Devices

Perform the following procedure to configure settings to apply to ALL Mobile Devices:

1. Click the **Global Settings** tab.

   The Global Settings display.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1dbe11055e36abf70c080ccc384f820c1a3e3baf%2Fadmin_mobiledevices_systemsettings.png?alt=media)
2. 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)
3. Uncheck the **Allow unlock with Biometric on supported devices** checkbox (checked by default), if this is not required.
4. Tick the **Allow Card Number only barcodes** checkbox if required, then select the pre-configured **Card Type** from the **Card Type for Card Number matching** drop-down menu.
5. Tick the **Allow QR Code Access Tokens** checkbox if you require the camera/barcode scanner on the mobile client (both iPhone and Android) to read QR Access Tokens (as created using the Card Editor). See "QR Code Readers" in the *Configuration Client User Guide* for further detail.
6. If you intend using the Mobile Evacuation feature to allow your site to move cardholders outside the system, ensure the Allow moving cardholders outside of the system checkbox is checked.

   **Note:** Operators also require the "Manage Cardholder Location" operator privilege to enable this feature to work.
7. In the **Mobile Reader - Permitted Card Technology and NFC** section, all card technologies are enabled by default.

   Uncheck any card technologies you do not require the Mobile Reader to be able to read.

   **Note:** The PIV option will only display if your site is licensed for PIV card functionality.
8. Select the **Use MIFARE Serial Number as Card Data** check box if required. If selected, Mobile Readers treat a card's Card Serial Number (CSN) as its card number when no Gallagher-encoded data is present on the card.
9. If you selected the **Use MIFARE Serial Number as Card Data** check box, select a **Card Type** from the drop-down list. Command Centre uses this Card Type's Facility Code to associate CSNs with Cardholders.
10. The **Enable built-in NFC card reader on supported mobile devices** option is enabled (checked) by default. If you require Mobile Readers to read MIFARE Plus, MIFARE DESFire, or PIV cards, leave it enabled. To hide the option for Mobile Readers to read these card technologies, deselect the checkbox.
11. The **Enable Mobile Credential reader on supported mobile devices** option is enabled (checked) by default. If you require Mobile Connect credentials to be read from Mobile Readers, leave it enabled.
12. Click each tab in turn and configure the Global Settings as required:
    * [Cardholders tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/cardholders-tab.md)
    * [Access Reader tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-devices-global-settings/access-reader-tab-ngc.md)
13. Click the **Save** button.


---

# 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/mobile-devices-global-settings.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.
