> 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/5-manage-apple-employee-badges.md).

# 5. Manage Apple Employee Badges

An operator can change the state of an Apple Employee Badge in Command Centre.

An Apple Employee Badge provisioned to the phone and watch will appear as two independent virtual DESFire credentials in Command Centre. Each credential can be managed independently of the other, by the operator or the Cardholder. Each credential will have a unique 21-character card number, as known as the credential identifier.

### Credential Identifier

V-UUUUUU-II-DD-CCCCCCCCCC

V = Version

U = Unique Site Identifier

I = Issue Level

D = Device Type (where 01 is iPhone and 02 is Apple Watch)

C = Card Number

**Note:** When mapping the credential identifier to a third-party system, (e.g. print system) it is recommended, the whole card number be passed.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-757ecf3350ded2ca86d3af9e01490fe815a4e193%2Fcardholdercardstile.png?alt=media)

### Cardholder Apple Employee Badge states

The credential can be placed into the following states by the Cardholder:

<table><thead><tr><th width="183">State</th><th>Description</th></tr></thead><tbody><tr><td>Suspended by user</td><td><p>When the Cardholder places their device into Lost Mode, their Apple Employee Badge will transition into the ‘Suspended by user’ state in Command Centre.</p><p><strong>Note:</strong> An operator belonging to an Operator Group with the privilege 'Override Card Status' can change the 'Suspended by user' state. The operator may want to change the state to 'Disabled (manually)', meaning when the phone exits Lost Mode (Cardholder authenticates at their phone), the credential won’t return to its previous 'Active' state. If the phone does not have internet connectivity when Lost Mode is exited, the credential will remain active in the wallet but will be disabled in Command Centre and cannot be used to request access.</p><p>If an operator changes the 'Suspended by user' state to 'Active', the state change is queued in the Apple Cloud and will not take effect until the Cardholder exits Lost Mode (Cardholder authenticates at their phone). This is the same behaviour as the credit card – the card cannot be used when the phone is in Lost Mode.</p></td></tr><tr><td>Active</td><td><p>When the Cardholder adds their Apple Employee Badge to the Wallet app, it is added in the ‘Default’ state, set on the Card State Set.</p><p>By default, the ‘Default’ state is ‘Active’ but this can be changed. If the ‘Default’ state is changed to ‘Disabled (manually)’ badges are added in a ‘Disabled’ state.</p><p>If the Cardholder finds their device after placing in Lost Mode (Cardholder authenticates at their device), their badge will resume, (i.e. change from ‘Suspended by user’ to ‘Active’).</p></td></tr><tr><td>Removed by user</td><td>The Cardholder can remove their Apple Employee Badge from the Wallet app on each device, or by logging onto iCloud and removing from there.</td></tr></tbody></table>

**Note:** If the Cardholder removes the credential from their Wallet, the credential is removed in Command Centre.

### Admin Apple Employee Badge states

The credential can be placed into the following states by the Command Centre operator:

<table><thead><tr><th width="183">State</th><th>Description</th></tr></thead><tbody><tr><td>Not yet Active</td><td><p>The Apple Employee Badge 'From' date us in the future.</p><p>The Apple Employee Badge displays the following message in the Wallet app.:</p><p><em>"This badge cannot be used. Gallagher has suspended use of this badge"</em></p></td></tr><tr><td>Active</td><td><p>The Apple Employee Badge is active.</p><p>The Apple Employee Badge displays as usable in the Wallet app.</p></td></tr><tr><td>Expired</td><td><p>The Apple Employee Badge ‘Until’ date is in the past.</p><p>The Apple Employee Badge displays the following message in the Wallet app:</p><p><em>"This badge cannot be used. Gallagher has suspended use of this badge"</em></p></td></tr><tr><td>Disabled (manually)</td><td><p>The Apple Employee Badge has been disabled by the operator.</p><p>The Apple Employee Badge displays the following message in the Wallet app:</p><p><em>"This badge cannot be used. Gallagher has suspended use of this badge"</em></p></td></tr><tr><td>Custom</td><td><p>All custom card states are inactive card states.</p><p>The Apple Employee Badge displays the following message in the Wallet app:</p><p><em>"This badge cannot be used. Gallagher has suspended use of this badge"</em></p></td></tr></tbody></table>

**Notes:**

* By default, Apple Employee Badges are provisioned into the Wallet app in an active state. For example, if the operator disables an Apple Employee Badge, then the Cardholder removes the badge from the Wallet app, then adds it back, the badge will be added in an active state. If the operator doesn’t want the Cardholder to provision an Apple Employee Badge, they must de-authorise the Cardholder, or assign the Cardholder a mobile credential that doesn’t allow provisioning of an Apple Employee Badge.
* If the operator unauthorizes the Cardholder, all badges assigned to the Cardholder will display as "Suspended" in the Wallet app.
* If a Cardholder suspends their Apple Employee Badge, (i.e. places their device into Lost Mode), then an operator with the "Override Card Status" privilege activates the Cardholder's badge, the Cardholder must first unlock their device, before it can be used at the reader.
* Cardholder **First Name** and **Last Name** is stored in the Gallagher Cloud. If a Cardholder record is deleted or redacted, the Cardholder's **First Name** and **Last Name** (used to provision the badges) are purged from the Gallagher Cloud.

### Account Binding

The Gallagher Apple Employee Badge solution employs strong account binding and a badge device transfer limit to prevent fraudulent use of Apple badges.

As a result, a cardholder cannot transfer their provisioned Apple badge to a different iCloud account. Additionally, a device migration limit is enforced to prevent badge duplication across devices (phone or watch). Only one device transfer limit can occur within a 90-day period. This limit is enforced after the first transfer, meaning a user can provision a badge to their device, migrate to another device, then the 90-day period is enforced.

For further detail refer to the **Removing Apple Account Binding** procedure (under *Using Command Centre* > *Working with Viewers* > *Cardholder Viewer*) in the Command Centre Client help file.


---

# 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/5-manage-apple-employee-badges.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.
