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

# Bulk Random Selection items

Bulk Random Selection items allow an operator to run a configured selection rule to randomly select multiple Cardholders at once from a pool of eligible Cardholders. Eligible Cardholders are defined by the selection criteria specified in the rule’s configuration.

Each eligible Cardholder has a probability of being selected as is defined in the rule’s configuration. For example, if the probability is set to 20%, each eligible Cardholder has a 20% chance of being selected. Each time an operator runs a Bulk Random Selection, they are given the opportunity to modify the probability, as well as the maximum number of Cardholders to be selected.

Upon a Cardholder being selected, the rule can optionally disable or expire a specific Competency, as defined in the rule’s configuration. The Personalised Notifications feature can be used to notify Cardholders that their Competency was disabled or expired. This allows, for example, a site to implement a policy where Cardholders are randomly selected to perform a test or certification to re-enable their access (Competency). The rule has settings to limit how frequently a Cardholder is selected and how many Cardholders are selected.

Bulk Random Selection rules can be run manually from the Random Selection administration viewer, Site Plans, and Status Tiles. They can be run automatically by Macros (e.g. on a schedule).

***

### Operator Privileges

An Operator requires the appropriate Random Selection privileges to perform Bulk 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 Bulk Random Selection items</td></tr><tr><td>"Run Bulk Random Selection"</td><td>run Bulk Random Selection items</td></tr><tr><td>"View Random Selection"</td><td>view Bulk Random Selection Items.</td></tr></tbody></table>

**Note:** Operators also require the View Site privilege to configure a Bulk Random Selection item, as well as the privileges to view any items (e.g. Access Groups, Access Zones, Card Types) that must influence the selection criteria.

***

### Reports

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

* Cardholder Random Selection
* Cardholder last Random Selection Time

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

* 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

Operators who are privileged to run a Bulk Random Selection can override the ‘Cardholder Probability of Selection’ and ‘Per-Run Total Cardholder Selection Limit’ settings when running the selection.

***

### Configuration

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

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

To configure Personalised Notifications so that Cardholders are notified when they are selected, refer to the topic *"Overall Process - Setting up Notifications"* in the Gallagher Configuration Client Help.

***

### View Status and Run a Bulk Random Selection item

You can add Bulk Random Selection items to a Status tile and perform the 'Run Selection' override as required.

Perform the following procedures to add Bulk 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>Running a Bulk Random Selection item</summary>

### Pre-requisites

Before you can override a Bulk Random Selection item from a Status tile, ensure that the Bulk Random Selection item(s) is/are added to the Status tile. Refer to [Status Tile actions](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/tile-actions/status-tile-actions.md).

### Procedure

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-2003b5deb674236e079dea62b0d32eacad93ae7c%2Fbulkrandomselection-icon.png?alt=media) button of the Bulk Random Selection item you want to override.

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

   The Bulk Random Selection window displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ed3f739b49be3bfad7ca57c77f08c062da90ad1a%2Fbulkrandomselection-override.png?alt=media)

   **Note:** The only override available is 'Run Selection'.
3. If required, change the **Cardholder Probability of Selection**. This is the probability that each eligible Cardholder will be selected.
4. If required, check, uncheck, or change the **Per-Run Total Cardholder Selection Limit**. This limits how many Cardholders can be selected in this run.

   **Notes:**

   * These two settings default to how they are configured against the Bulk Random Selection item. Changing these settings here will not change how they are configured against the Bulk Random Selection item, i.e. the changes will apply to this run only.
   * If this Bulk Random Selection is configured with a Competency, a warning displays informing you that Cardholders' Competencies may be expired or disabled.
5. Click **OK** to run the Bulk Random Selection.

   An event is raised for each Cardholder that is selected. Check the Event Trail tile to see which Cardholders were selected.

</details>

***

### Bulk Random Selection Rule Priority

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

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

<table><thead><tr><th width="75">Priority</th><th width="480">If...</th><th>the Cardholder is...</th></tr></thead><tbody><tr><td>1</td><td>The Bulk Random Selection has a 0% <strong>Cardholder Probability of Selection</strong></td><td>Not selected</td></tr><tr><td>2</td><td><strong>Per-Run Total Cardholder Selection Limit</strong> has already been reached in this run (the run has complete)</td><td>Not selected</td></tr><tr><td>3</td><td><strong>Periodic Total Cardholder Selection Limit</strong> (e.g. 20 selections per day) has been reached</td><td>Not selected</td></tr><tr><td>4</td><td><strong>Per-Cardholder Selection Limit</strong> (e.g. once every 12 hours) has been reached</td><td>Not selected</td></tr><tr><td>5</td><td>The Cardholder meets one of the conditions added on the <strong>Bulk Random Selection</strong> tab</td><td>Randomly selected (in accordance with Probability %)</td></tr><tr><td>6</td><td>There are no conditions added on the <strong>Bulk Random Selection</strong> tab</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/bulk-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.
