> 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/quick-tips-for-working-with-random-selection-items.md).

# Quick Tips for working with Random Selection items

### Overview

The Random Selection feature introduces two items: Random Selection items and Bulk Random Selection items.

***

### Random Selection items

* A Random Selection item allows Command Centre to randomly select Cardholders based on the probability percentage configured against their Access Groups(s) when badging a credential at nominated Doors.
* You can configure several factors that contribute to whether a Cardholder is selected or not.
* You can configure whether access is granted or denied after a Cardholder is selected at a Door.
* You can configure events to be raised if a Cardholder fails to enter a specific Access Zone after being selected. This can be paired with a custom message displayed on Readers after being selected, to instruct Cardholders to go to that zone.

**Random Selection tab**

* Add the Doors to which your configured Random Selection Rules apply.
* Add and configure the Rules that define the Random Selection behaviour for different Access Groups.

**Overdue Arrival tab**

* Configure events to be raised if a Cardholder does not access a specified Access Zone after being randomly selected.

**More information**

For more information, refer to the topic *"Random Selection items"* in the Gallagher Command Centre Help.

***

### Bulk Random Selection items

* A Bulk Random Selection item allows Command Centre to randomly select multiple Cardholders at once based on a probability percentage.
* Bulk Random Selection items can be run manually by operators or automatically using Macros.
* You can configure several factors that contribute to whether a Cardholder is selected or not.
* You can configure events to be raised if a Cardholder fails to enter a specific Access Zone after being selected. The Personalised Notifications feature can be used to notify Cardholders that they were selected, so they know to go to that zone.

**Bulk Random Selection tab**

* Add the selection criteria to define which Cardholders may be selected by the Bulk Random Selection.
* Configure the Cardholder Probability of Selection to define each eligible Cardholder's probability of being selected.
* Optionally, add a Competency to be expired or disabled upon selection, and configure the 'limit' options.

**Overdue Arrival tab**

* Configure events to be raised if a Cardholder does not access a specified Access Zone after being randomly selected.

**Hint**

To test the Bulk Random Selection once you have configured it, uncheck the **Set Competency Upon Selection** check box, then click the **Run Selection** button. Check an Event Trail tile to review the selection and quantity of Cardholders that were selected.

**More information**

For more information, refer to the topic *"Bulk Random Selection items"* in the Gallagher Command Centre Help.


---

# 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/quick-tips-for-working-with-random-selection-items.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.
