> 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/licensable-features/apple-employee-badge.md).

# Apple Employee Badge

### Introduction

The Apple Employee Badge solution is for specific customers only. Please contact your local Gallagher representative if you’re interested in adopting this solution.

This solution allows Cardholders to add an Apple Employee Badge to Apple Wallet on their compatible iPhone and Apple Watch to request access using NFC at doors, elevators, turnstiles, and other facilities at their corporate workplaces.

***

### Licensing

The Apple Employee Badge solution is a licensable feature. To configure this solution in Gallagher Command Centre the following license strings are required:

`[Features]`\
`Apple Pass=1`

`[Limits]`\
`Mobile Credentials=X` (Where `X` is the number of mobile credentials that can be assigned to Cardholders)

***

### Features and Functionalities

Solution features and functionalities are:

* Use NFC from your iPhone or Apple Watch when requesting access at the reader.
* Use Apple Express Mode to request access without unlocking their iPhone. Apple badges are provisioned by default in Express Mode.
* Gallagher Command Centre can be configured to require second factor (2FA) at the reader. When 2FA is enforced, the user must present a second factor (Face ID, Touch ID, or Passcode) when requesting access.
* Use Apple Power Reserve Mode to request access when your iPhone needs a charge. Power Reserve provides up to five hours of access, so you can still get inside.

  **Note:** Power Reserve Mode only works for the user’s default wallet credential, (i.e. usually the credit card).
* Cardholders can view and manage their Apple badge on their iPhone, Apple Watch, ot by logging into their iCloud account from any PC. Cardholder management functions are adding a badge, suspending a badge, resuming a badge, and removing a badge.
* Operators can view and manage Apple badges in Command Centre. Operator management functions are suspending a badge, resuming a badge, and removing a badge.
* Supports one iPhone and one Apple Watch per Cardholder.
* Supports two factor authentication at the reader. Two factor authentication can be configured always on, or according to a schedule. When two factor authentication is enforced, the Cardholder must present a second factor (Face ID, Touch ID, or Passcode).
* Supports double card overrides at the reader.
* Supports Cardholder First Name and Last Name updates to the Apple badge. Supports regeneration of Apple Keys, and Apple badge artwork updates.
* Provides a secure credential. The credential data is protected by the device’s Secure Element (SE). The SE is a dedicated chip that is physically isolated from the main processor, specifically designed to handle sensitive transactions like those in Apple Pay.
* The Shareable Keys section (on the **Mobile Wallet** tab of the Server Properties) enables the retrieval of an Apple Read Key from Command Centre, which can then be programmed at a third-party reader, allowing Apple credentials to be read at the reader. Using Apple credentials, an employee can authenticate at all readers onsite.

***

### Prerequisites

Solution prerequisites are:

* The Gallagher Command Centre system must be version 9.10 MR3 (or later).
* The Command Centre server must be connected to the Gallagher Cloud and Gallagher API Gateway. Refer to [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for further details.
* Command Centre Customer Experience Improvement Program (CEIP) must be enabled.
* The site must be using supported Gallagher Multi-Tech readers.
* The Gallagher Mobile Connect app (or SDK) must be installed on the Cardholder's iPhone.
* The Cardholder's iPhone must be iPhone 8 or later running iOS 16 or later.
* The Cardholder's Apple Watch must be Watch Series 5 or later running watchOS 10 or later.
* The Cardholder must have an active iCloud account (Apple ID).

***

### Limitations

* It is recommended that Apple Employee Badge be assigned to permanent employees not visitors, as is the purpose of the badge. The Apple Employee Badge is not removed when a visitor is marked offsite, however the visitor is removed from all Access Group assignments when marked offsite, meaning the visitor will be unable to gain access. It is recommended that a separate Mobile Credential Type be created for visitors, that doesn’t allow provisioning of the Apple Employee Badge Type.
* 2FA is not supported by Apple Employee Badge when the Gallagher reader is assigned to an Elevator Car.

***

This section covers the following configuration steps:

[1. Configure Apple Keys](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/1-configure-apple-keys.md)

[2. Configure Mobile Wallet Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/2-configure-mobile-wallet-readers.md)

[3. Configure the Apple Employee Badge Type](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/3-configure-the-apple-employee-badge-type.md)

[4. Enable In-app Apple Employee Badge Provisioning](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/4-enable-in-app-apple-employee-badge-provisioning.md)

[5. Manage Apple Employee Badges](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/5-manage-apple-employee-badges.md)

[6. Report Apple Employee Badge Assignments](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/apple-employee-badge/6-report-apple-employee-badge-assignments.md)


---

# 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/licensable-features/apple-employee-badge.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.
