> 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/4-enable-in-app-apple-employee-badge-provisioning.md).

# 4. Enable In-app Apple Employee Badge Provisioning

The Apple Employee Badge Type is linked to a mobile credential (refer to the section above). Assignment of a mobile credential is required to authenticate the Cardholder, and to enable download of the Mobile Connect app used to provision an Apple Employee Badge into the Wallet app.

**Important:** When the Cardholder provisions an Apple Employee Badge into the Wallet app, the organisation will be charged a fee.

### Procedure

This procedure describes how to enable in-app Apple Employee Badge provisioning, as follows:

1. Assign the Cardholder a mobile credential that enables in-app provisioning of the Apple Employee Badge.

   For details on how to assign a mobile credential refer to the topic *"Assigning a Card, Credential, or Digital ID"* in the Command Centre Online Help.

   **Notes:**

   * If the mobile credential has any of the following states, the Cardholder will be unable to add an Apple Employee Badge to their Wallet app.:
     * Expired,
     * Disabled (manually),
     * Lost,
     * Stolen,
     * Damaged,
     * Disabled (unauthorized),
     * Invitation Expired,
     * Waiting for Registration, or
     * a custom card state.
   * If the Cardholder is not authorised, meaning the mobile credential state is Disabled (unauthorized), the Cardholder will be unable to add an Apple Employee Badge to their Wallet app.
2. The Cardholder receives the mobile credential email invitation and downloads the Mobile Connect app.

   **Note:** The **Add to Apple Wallet** button will **not** show at this point, as the Cardholder hasn’t been authenticated.
3. The Cardholder navigates back to the email invite and selects the **Accept Credential** button.

   The Cardholder may be required to enter a 6-digit confirmation code sent via SMS to verify their device.
4. The Cardholder will be required to specify the second factor to be used (Face ID, Touch ID, or Passcode). This must be entered at the phone when the reader requests a second factor using Bluetooth.

   **Note:** The second factor is optional if the invitation is created with the REST API.
5. The Cardholder selects the **Add to Apple Wallet** button.
6. The Cardholder must agree to the Terms and Conditions. These terms describe how the Cardholder’s organisation, as the Apple Employee Badge provider ("Participating Provider") will use certain personal information to enable the Cardholder’s usage of Apple Wallet with Command Centre.
7. The Cardholder selects the **Done** button.

### Result

The Apple Employee Badge will display within the Wallet app. The Apple Employee Badge is provisioned in Express Mode, meaning the device needn’t be unlocked, or the Wallet app open to request access at the reader.

To view the information on the rear of the Apple Employee Badge, select the Information Icon, top right of the badge. The rear of the badge displays. To remove the badge, scroll down and select **Remove Badge**.

To use the Apple Employee Badge, present the phone or watch at the reader.

**Note:** If the Mobile Connect app is open in the foreground, Apple Employee Badge will not be used to communicate with the reader, Bluetooth® will be used instead.


---

# 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/4-enable-in-app-apple-employee-badge-provisioning.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.
