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

# Random Selection items

Random Selection items allow Command Centre to randomly select Cardholders, based on the probability percentage configured against their Access Group(s), at nominated Doors upon entry (i.e. when accessing a Door's Entry Zone). You can configure the Random Selection item to randomly select Cardholders at all times or during scheduled hours only.

When the Cardholder is selected, the T20 Terminal displays the configured message. If the Require acknowledgement check box is selected, the Cardholder must press the button to acknowledge the message before being granted/denied access.

Depending on your configuration, Command Centre can either grant or deny access, and either expire or disable the Cardholder's Competency, upon selection.

Random Selection items can also be configured to randomly select Cardholders while the Controller is offline.

Random Selection items can be used in conjunction with the licensed 'Alcolizer' feature to randomly select Cardholders for Breath Alcohol Concentration (BrAC) testing. Selected Cardholders can be denied access and required to pass a BrAC test before having their competency re-enabled.

For details on how to configure the Alcolizer feature of Command Centre, refer to the Alcolizer release note provided with the Alcolizer release.

### Operator Privileges

An Operator requires the appropriate Random Selection privileges to perform Random Selection item tasks. The privileges only apply within the Divisions assigned to that Operator Group.

<table><thead><tr><th width="234">Operator Privilege...</th><th>is required to...</th></tr></thead><tbody><tr><td>"Edit Random Selection"</td><td>modify Random Selection items</td></tr><tr><td>"View Random Selection"</td><td>view Random Selection items.</td></tr></tbody></table>

**Note:** Operators require View Site, View Schedule, and View Access Groups privileges to configure a Random Selection item.

***

### Reports

The following Cardholder Report filters are applicable to Random Selection items:

* Cardholder Random Selection
* Cardholder last Random Selection Time

The following Cardholder Report columns are applicable to Random Selection items:

* Random Selection Name
* Last Selected Time
* Last Selected Event Summary
* Last Selected Time (*Random Selection Name*)

**Notes**

* We recommend that 'Last Selected Time (*Random Selection Name*)' columns are not used alongside other Random Selection columns in the same report.
* We recommend that reports using these Random Selection columns are not combined with other event columns or event filters.

***

### Considerations

* The T20 Terminal and the Door must be connected to the same Controller. Otherwise, the T20 does not display feedback correctly.
* If the 'Repeat last selection action' value is greater than the 'maximum selection limit' value, then 'Repeat last selection action' takes priority. This means, for the duration of the 'Repeat last selection action', the last selection action is always repeated.
* When an Alarm Zone is in Armed mode, it is still disarmed upon a valid credential-badge at a monitored Terminal even if access is denied due to random selection.

***

### Configuration

To configure a Random Selection item, perform the following procedures in Command Centre Client:

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

[Removing a Door or a rule](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/random-selection-items/removing-a-door-or-a-rule.md)

***

### View Status and Override a Random Selection item

You can add Random Selection items to a Status tile and override them as required. The override options are: Selection On, Selection Off, and Cancel Override.

Perform the following procedures to add Random Selection items to a Status tile and perform an override:

<details>

<summary>Adding items to a Status Tile</summary>

Items can be added to the Status tile, as follows:

1. Click the **Add Item** button.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6f1e69f828ab0f8460d44d9538a6f8f7436f1e62%2Fselectspecificsource_popup.png?alt=media)
2. Search for the item(s) you want to add to this tile by entering search criteria in the **Search** field and/or refining the filters.

   The grid becomes populated with items that match the search criteria.
3. Click the checkbox next to each item name you want to include, or click the **Select All** button if you want to include all items.

   **Note:** In a multi-server environment, remote reports are unable to be added to a local server's Status tile.
4. Click the **Add Selection** button.

   The pop-up closes and the item(s) now appears in the list of items on the Status tile.

**Note:** You can also drag items from a Site Plan tile into this tile.

</details>

<details>

<summary>Override a Random Selection item</summary>

### Pre-requisites

Before you can override a Random Selection item, ensure that the Random Selection item(s) is/are added to the Status tile. Refer to Status Tile actions.

1. Click the ![Random Selection - remove door.jpg](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c1bc2e4114d3275f71046f344eb26b9d250b1db1%2Frandomselection-icon.png?alt=media) button of the Random Selection item you want to override.

   The Random Selection menu displays.
2. Select **Overrides**.

   The Random Selection window displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1dfd40ebac25c60ae7c922f5cadf29771a8c6276%2Frandomselection-override.jpg?alt=media)
3. Configure as required.

   <table><thead><tr><th width="196">To...</th><th>then...</th></tr></thead><tbody><tr><td>override to on</td><td>Select <strong>Selection On</strong>, then click <strong>OK</strong>.<br>The Status column of the item reads: "Selection: On (Since DD/MM/YYYY HH:MM AM/PM). Selected Cardholders N.</td></tr><tr><td>override to off</td><td><ol><li>Select <strong>Selection Off</strong>.</li><li><p>You can either:</p><ul><li>Click the <strong>Until this time</strong> radio button, and enter the time of day you want the override to end, or</li><li>Click the <strong>For</strong> radio button, and enter the hours and/or minutes you want selection to be off for (this is limited to a maximum of 23 hours and 59 minutes).</li></ul><p>The Status column of the item reads: "Selection: Off (Since DD/MM/YYYY HH:MM AM/PM). This item has been overridden until DD/ MM/YYYY HH:MM AM/PM."</p></li></ol></td></tr><tr><td>cancel override</td><td>Select <strong>Cancel Override</strong>, then click <strong>OK</strong>.<br>The Status column of the item reads: "Selection: On/Off (Since DD/MM/YYYY HH:MM AM/PM). Selected Cardholders N.</td></tr></tbody></table>

</details>

***

### Random Selection Rule Priority

The following is intended to demonstrate the order of priority that Random Selection items give to various factors when selecting Cardholders.

Priority is listed from 1 = highest priority, to 9 = lowest priority.

<table><thead><tr><th width="75">Priority</th><th width="482">If...</th><th>the Cardholder is...</th></tr></thead><tbody><tr><td>1</td><td>Random Selection item status is Off</td><td>Not selected</td></tr><tr><td>2</td><td>Cardholder was selected within the <strong>Repeat last selection action</strong> time (e.g. 5 minutes) ago</td><td>Always selected</td></tr><tr><td>3</td><td>Cardholder is in an Access Group with a 0% <strong>Probability %</strong></td><td>Not selected</td></tr><tr><td>4</td><td><strong>Set total cardholder maximum selection limit</strong> (e.g. 50 selections per hour) has been reached</td><td>Not selected</td></tr><tr><td>5</td><td><strong>Set each cardholder maximum selection limit</strong> (e.g. once every 12 hours) has been reached</td><td>Not selected</td></tr><tr><td>6</td><td>Cardholder has not been selected within the <strong>Enforce cardholder selection</strong> duration (e.g. once every 365 days) and <strong>Ignore cardholders that have never been selected</strong> is deselected</td><td>Always selected</td></tr><tr><td>7</td><td>Cardholder (who has previously been selected at least once) has not been selected within the <strong>Enforce cardholder selection</strong> duration (e.g. once every 365 days) and <strong>Ignore cardholders that have never been selected</strong> is selected</td><td>Always selected</td></tr><tr><td>8</td><td>Cardholder is in an Access Group with a non-zero Probability % and status is On</td><td>Randomly selected (in accordance with Probability %)</td></tr><tr><td>9</td><td>Cardholder is not in an Access Group with a Random Selection rule configured against it, but a Random Selection rule is configured with <strong>Applies to all access groups</strong> selected. This Random Selection Rule has a non-zero probability, and status is On</td><td>Randomly selected (in accordance with Probability %)</td></tr></tbody></table>


---

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