> 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/random-selection.md).

# Random Selection

The licensed Random Selection feature introduces two methods of randomly selecting Cardholders. A site may wish to select Cardholders for, for example, completion of a test or renewal of a certification. If the site wants to select Cardholders randomly without manually choosing them, as to remain unbiased, the different Random Selection methods can be used:

**Random Selection**

A 'Random Selection' item can be configured to give certain Cardholders a chance of being selected when they access certain doors. Which Access Groups' Cardholders may be selected, and their probability of being selected, as well as the Doors at which they can be selected, are all configurable. Optionally, Cardholders can have a specified Competency expired or disabled when they are selected. There are also options that can be configured to ensure Cardholders are not selected too often or too infrequently.

* Selection requires no operator action.
* Only Cardholders on site and attempting access can be selected.
* Cardholders are immediately made aware they were selected, and can be denied access.

**Bulk Random Selection**

A 'Bulk Random Selection' item can be configured to be run manually by operators or on a schedule using Macros, to randomly select multiple Cardholders at once. When the Bulk Random Selection is run, every eligible Cardholder has a chance of being selected according to the configured probability. Cardholder eligibility can be defined using simple or complex criteria. For example, the Bulk Random Selection could be configured so only Cardholders in a certain Access Group are eligible for selection. Optionally, Cardholders can have a specified Competency expired or disabled when they are selected. There are also options that can be configured to limit how many Cardholders are selected and ensure Cardholders are not selected too often.

* Selection requires operator action or Command Centre server action (with scheduled Macros).
* Cardholders on site and/or off site can be selected, whether attempting access or not.
* Cardholders rely on the Personalised Notifications feature, or other manual means, to be made aware they were selected.

Select the item below that you require further detail on:

[Random Selection items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/random-selection-items.md)

[Bulk Random Selection items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/bulk-random-selection-items.md)

***

### Licensing

'Random Selection' is a licensable feature, i.e. your license file must contain the following entry:

`[Features]`\
`Random Selection=1`


---

# 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/random-selection.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.
