> 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/products/cc-software/operate/command-centre-random-cardholder-selec.md).

# Random Cardholder Selection vs Random Selection

Compare Command Centre random-selection features, versions, licensing, and migration requirements.

#### What is the difference between Random Cardholder Selection and Random Selection?

These are two similarly-named features for randomly selecting cardholders at a door, for example for random screening. The key difference is **where the logic runs**. **Random Cardholder Selection** is **server-based** (the server and controller must both be online). **Random Selection** is **controller-based** (it works even when the controller is offline to the server).

Random Selection is the **current core feature** (`C12824`). Random Cardholder Selection (`C12583`) is the older customisation being migrated away from. **They cannot run on the same door at the same time.**

***

## Comparison

|                       | Random Cardholder Selection                                                                                                                                                                                        | Random Selection                                                               |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
| **Main difference**   | Server based. Server **and** controller need to be online to work properly.                                                                                                                                        | Controller based. Works even when the controller is **offline** to the server. |
| **Available version** | v7.01 to v8.30 or later                                                                                                                                                                                            | v8.30 or later (not available in v8.20)                                        |
| **Licensing string**  | <p><code>\[Limits]</code><br><code>Competencies=X</code><br><code>\[Features]</code><br><code>RandomCardholderSelection=1</code><br><code>\[Customisations]</code><br><code>RandomCardholderSelection=1</code></p> | <p><code>\[Features]</code><br><code>Random Selection=1</code></p>             |

### Exception: v8.10 customisation

Random Selection is also available as a **customisation only in v8.10**, with the licence string:

```
[Customisations]
Random Selection=1
```

### Important: not on the same door

Random Cardholder Selection and Random Selection **cannot work on the same door at the same time**. You can have both customisations in v8.10 at the same site, but the two customisations should **not** be configured onto the same door.

***

## Migration: customisation to core

<table><thead><tr><th>Customisation</th><th width="40">→</th><th>Core</th></tr></thead><tbody><tr><td><code>C12583</code> LIC Random Cardholder Selection</td><td>→</td><td><code>C12824</code> LIC Random Selection</td></tr></tbody></table>

The migration step for customers currently using the customisation is provided in **v8.30**, as this is the last version in which the customisation is upgraded. From **v8.40**, customers should be using **`C12824`** (the core Random Selection feature).

***

🔗 **Related**

* [Command Centre - Access Groups](/knowledge-hub/products/cc-software/configure/command-centre-access-groups.md). How access at a door is granted.


---

# 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/products/cc-software/operate/command-centre-random-cardholder-selec.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.