> 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/creating-a-random-selection-item-and-configuring-a-rule.md).

# Creating a Random Selection item and configuring a rule

### Pre-requisites

Before proceeding with this procedure, ensure the following pre-requisites have been configured:

* The Door(s) that will be used to randomly select Cardholders. Refer to the topic "Creating Doors" in the *Gallagher Configuration Client Online Help*.
* The Access Group(s) containing the Cardholders that will be randomly selected. Refer to "Setting up Access Groups" in the *Gallagher Configuration Client Online Help*.
* The Output Schedule(s) for Access Group(s) to be selected within. Refer to "Creating a new Schedule" in the *Gallagher Command Centre Online Help*.

Optionally configure the following:

* The Competency that will be disabled or expired when a Cardholder is randomly selected. Refer to "Configuring Competencies" in the *Gallagher Configuration Client Online Help*.
* The Alcolizer utility (can be used in conjunction with Random Selection). Refer to the release note 'Release Note Alcolizer (v8.30).pdf' provided with the Alcolizer release.
* The Access Groups containing the Cardholders that will be exempt from selection. Refer to "Setting up Access Groups" in the *Gallagher Configuration Client Online Help*.

### Configuring the Random Selection tab

Perform the following procedure to create a Random Selection item and configure a rule:

1. From Command Centre main window, click **Administration** > **Random Selection**.
2. Click the **New Random Selection** button and select Random Selection.

   The Random Selection Configuration window displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-bf319225548f640607a18b34c5b580d3d4077ad2%2Frandomselection-rsconfiguration.jpg?alt=media)
3. Enter a Name and Description, and select a Division. Then, click Close.
4. Click the ![Random Selection - add door](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a9d4c8014cd5285e530807af37559eb89f1220e0%2Frandomselection-adddoor.jpg?alt=media) button to add the Doors that will be used to Randomly select Cardholders.

   The Select Doors window displays, listing the selectable Door(s).

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f5e224db37748b01b8d606be69cc9edcc5e7abc0%2Frandomselection-selectdoor.jpg?alt=media)
5. Select the checkbox(es) of the required Door(s), then click the **Add Selection** button.

   **Notes:**

   * Cardholders may be randomly selected only when entering the Doors' Entry Zones; not Exit Zones.
   * You can add a maximum of 30 Doors to a Random Selection item. Otherwise, the error message "Changes have not been saved: Random Selection item can only support up to 30 Doors" displays.
6. Click the ![Random Selection - add door](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a9d4c8014cd5285e530807af37559eb89f1220e0%2Frandomselection-adddoor.jpg?alt=media) button to add a Random Selection rule.

   The Add Random Selection window displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fe42050bf870253e3881ae8c7e0cf7e6ee6270b5%2Frandomselection-addrs.jpg?alt=media)
7. **Options are:**
   * Configured Access Groups
   * Applies to all access groups (default option).

<details>

<summary>Applies to all access groups</summary>

**Applies to all Access Groups**

This rule applies only to those Access Groups that don't have a Random Selection rule explicitly configured against them.

**Example**

Three Access Groups are configured in Command Centre: Access Group - 1, Access Group - 2, and Access Group - 3.

Two rules are configured:

**Options Schedule Probability %**

*Applies to all access groups* Applies at all times 20.0

Access Group - 2 Applies at all times 50.0

The **Applies to all access groups** rule only applies to Access Groups -1 and Access Group -3.

</details>

Select the check box(es) of the Access Group(s) that the rule applies to, then click the **Add Selection** button.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-520587d1b58129a4bd31b750816d66b182b1be95%2Frandomselection-addrs2.jpg?alt=media)

The Select Schedule window displays.

8. Select the radio button of the Output Schedule that you want to apply to this rule, then click **OK**.

   <table><thead><tr><th width="144">Options</th><th>Description</th></tr></thead><tbody><tr><td>Applies at all times</td><td>If selected, the Random Selection rule is ON at ALL times (i.e. 24/7).</td></tr><tr><td>Default Outputs Off</td><td>If selected, the Random Selection rule is OFF (i.e. Cardholders are not selected).</td></tr><tr><td>Your configured Output Schedule(s)</td><td>If selected, the Random Selection rule is ON during the scheduled hours only.</td></tr></tbody></table>

   **Notes:**

   * You can modify the rule's schedule later if required.
   * You can add a maximum of 50 rules to a Random Selection item. Otherwise, the error message "Changes have not been saved: Random Selection item can only support up to 50 rules" displays.
9. From the Probability % column, using the ![Random Selection - add door](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a6c274ce28010a7ca6035fe1440e6e2c7918ffd2%2Frandomselection-probabilitybutton.jpg?alt=media) buttons or manually, enter the probability percentage for this rule (valid range = 0.0 - 100).

<details>

<summary>Click here for information about Probability %</summary>

**Probability %**

The probability (of selection) percentage that is configured against the Access Groups.

**0.0%** - Cardholders who are members of an Access Group configured with 0.0% probability are **never** selected, even if they are also members of Access Groups with a non-zero probability.

**100%** - Cardholders who are member of an Access Group configured with 100% probability are **always** selected (unless maximum selection limit is reached).

The 'Applies to all' rule does not apply to Cardholders who are members of an Access Group explicitly defined in the Random Selection item.

For Cardholders who are members of multiple Access Groups, the Random Selection applies the **highest** percentage (except the 0.0% case mentioned above).

Child Access Groups always inherit their parent(s) probability %, except when the probability % configured against a Child Access Group is higher than the parent(s).

</details>

10. Configure the remaining parameters as required.

    **Note:** Some of the following parameters inform the selection decision (i.e. whether to select or not) each time a Cardholder is subjected to Random Selection. To see which parameters take priority over others, refer to the **Random Selection rule priority** section at the end of the [Random Selection](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection.md) chapter topic.

    <table><thead><tr><th width="150">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Selection Message</td><td>The text displayed on the T20 Terminal screen when a Cardholder is selected. This field is limited to 2048 characters.<br>To configure, in the <strong>Selection Message</strong> field, enter the message to be displayed on the T20 Terminal screen upon selection.</td></tr><tr><td>Require acknowledgement</td><td>If set, the Cardholder must press the <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a571300b75c0b4c1f8a5910cb92b91d04a4450c5%2Frandomselection-t20.jpg?alt=media" alt="Random Selection - remove door.jpg"> button on the T20 Terminal to acknowledge that they have read the message. If the message is not acknowledged before the configured timeout, then access is denied.</td></tr><tr><td>Timeout (seconds)</td><td>The maximum time allowed for a cardholder to acknowledge the message displayed on the T20 Terminal. Measured from card badge.<br>To configure, using the <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a6c274ce28010a7ca6035fe1440e6e2c7918ffd2%2Frandomselection-probabilitybutton.jpg?alt=media" alt="Random Selection - add door"> buttons or manually, enter the time (in seconds) in the <strong>Timeout (seconds)</strong> field after which the message on the T20 Terminal screen is cleared if not acknowledged (Default timeout is 10 seconds; valid range = 0 - 999).</td></tr><tr><td>Deny access on selection</td><td>If set, a Cardholder is denied access upon selection.</td></tr><tr><td>Set competency upon selection</td><td>If set, when a Cardholder is selected at a nominated Door upon entry, the Cardholder's Competency (as nominated in the configuration) is either expired or disabled, and an event is raised.<br>Competencies can be used to deny Cardholder access to specific areas until the Cardholder has been tested (e.g. Drug &#x26; Alcohol).<br>If using Alcolizer, the Competency is re-enabled on passing the alcohol test.</td></tr><tr><td>Set each cardholder maximum selection limit</td><td>The maximum number of times each <em>individual</em> Cardholder can be selected within a specified period of time.<br>To limit the maximum number of selections for any given Cardholder within a specific period of time, select the <strong>Set each cardholder maximum selection limit</strong> check box, and set the maximum <strong>Number of selections</strong> (valid range = 1–99, default = 3) a Cardholder can be selected within the <strong>Duration for selection</strong> (valid range = 0–365 days, 0–23 hours, defaults = 30 days, 0 hours).<br>Once the maximum selection limit is reached, the Cardholder is not selected until the specified period has ended.</td></tr><tr><td>Set total cardholder maximum selection limit.</td><td>The maximum number of selections that may occur across <em>all Cardholders</em> within a specified period of time.<br>To limit the maximum number of selections of all Cardholders within a specific period of time, select the <strong>Set total cardholder maximum selection limit</strong> check box, and set the maximum <strong>Number of selections</strong> (valid range = 1–99, default = 10) for all Cardholders within the <strong>Duration for selection</strong> (valid range = 0–99 hours, 0–59 minutes, defaults = 1 hour, 00 minutes).<br>Once the maximum selection limit is reached, no Cardholders are selected until the specified period has ended.</td></tr><tr><td>Enforce cardholder selection</td><td>If set, all Cardholders who have not been selected within the last configured duration (e.g. 365 days) will be selected at their next badge.<br>For example, if <strong>Enforce cardholder selection</strong> is selected and the duration is set to 365 days, if a Cardholder goes 365 days without being selected, they will be selected on their next badge.<br>If <strong>Ignore cardholders that have never been selected</strong> is selected, selection will not be enforced on Cardholders who have never been selected (e.g. new Cardholders). If <strong>Enforce cardholder selection</strong> is selected, but <strong>Ignore cardholders that have never been selected</strong> is <em>not</em> selected, all new Cardholders will be selected on their first badge.</td></tr><tr><td>Continue selection when Controller offline</td><td>If set, Command Centre continues to randomly select Cardholders while the Controller is offline.<br><br><strong>Note:</strong> If a Cardholder is selected while the Controller is offline, the state of their configured Competency does not change (e.g. expire or disable). Therefore, the Competency does not prevent subsequent access. Once the Controller is online, the Competency is processed.</td></tr><tr><td>Repeat last selection action</td><td>If set, Command Centre continues to repeat the latest selection decision for the configured duration OR until the Competency is expired or disabled. For example, if a Cardholder is randomly selected at a Door while the <strong>Repeat last selection action</strong> option is enabled for 5 minutes, the Cardholder will be selected every time they badge their card at that Door for the next 5 minutes, or until the Competency is expired or disabled. This prevents Cardholders quickly badging their card again after being randomly selected in an attempt to gain access before their Competency is expired or disabled.<br><br><strong>Note:</strong> If the Competency action cannot occur (because of a lock on the Cardholder record), the repeat last selection action stops and a "Random Selection Failed to Modify Cardholder" event is raised.</td></tr><tr><td>Use alcolizer</td><td>Appears when the licenced 'Alcolizer' feature is installed. Is only enabled if <strong>Require acknowledgement</strong> is selected.<br>If set, an alcohol test must be successfully be completed at an Alcolizer unit before access to the Door is granted.</td></tr></tbody></table>

<details>

<summary>Click here for more information if you are using Alcolizer</summary>

<table><thead><tr><th width="144">If...</th><th>then...</th></tr></thead><tbody><tr><td>Alcolizer unit is on the same Door as the Random Selection item</td><td><ul><li><strong>Use alcolizer</strong> should be selected.</li><li>The Door assigned to the Alcolizer unit and the Random Selection item should be set to 'Secure Mode'.</li><li><strong>Timeout</strong> represents the total time allowed for a cardholder to acknowledge the message displayed on the T20 Terminal and complete the alcohol test.</li><li>If the reader on the Door is non-T20, the prompt for alcohol testing will be displayed directly at the Alcolizer unit upon Cardholder badging.</li></ul></td></tr><tr><td>Alcolizer unit is on a Door different from the Random Selection item</td><td><ul><li><strong>Selection Message</strong> can be configured to inform Cardholders of the Alcolizer unit's location.</li><li>The Door assigned to the Alcolizer unit should be set to 'Dual Auth - No PIN' mode.</li><li><strong>Require acknowledgement</strong> can optionally be selected. If the reader on the Random Selection Door is non-T20, Cardholders will be denied access if Require Acknowledgement is selected.</li><li><strong>Use alcolizer</strong> should be left deselected.</li></ul></td></tr></tbody></table>

</details>

### Configuring the Overdue Arrivals tab

1. Click the **Overdue Arrivals** tab.

   On this tab you can configure alarms to be raised if a Cardholder does not enter one of your chosen Access Zone(s) after being selected by this Random Selection item. You can configure how much time they have before an alarm is raised.

   For example, you may require Cardholders to access a clinic within one hour of being randomly selected for medical testing. Otherwise, a Random Selection Overdue Arrival event will be raised.
2. Select the **Create events if cardholder does not...** check box.
3. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-91b1837bb0a2aeffc6ccef3863831c12a6418018%2F41090.png?alt=media) button to add the Access Zones that Cardholders must access after being selected. Entering one of these Access Zones will stop further alarms being raised.

   The Select Access Zones window displays, listing the selectable Access Zones.
4. Select the checkbox(es) of the required Access Zone(s), then click the **Add Selection** button.

   **Note:** You can add a maximum of 20 Access Zones for Overdue Arrivals per Random Selection item.
5. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-91b1837bb0a2aeffc6ccef3863831c12a6418018%2F41090.png?alt=media) button to add a Time Period.

   The Create Time Period window displays.

   **Notes:**

   * Time Periods define how much time will pass after a Cardholder is selected before an alarm is raised (note that alarms are not raised if the Cardholder accesses one of the selected Access Zone(s) before any Time Period has elapsed).
   * Network and server outages can delay the processing of Cardholder access events, causing Overdue Alarms to be raised even after a Cardholder has accessed one of the selected Access Zone(s).
   * Up to five Time Periods can be added, so alarms can be raised at several times until the Cardholder accesses one of the selected Access Zone(s).
6. Enter an amount of time for this Time Period, then click **OK**.

### Configuring the Action Plans/Alarm Instructions tab

1. Click the **Action Plans/Alarm Instructions** tab.
2. To configure the Action Plan or Alarm Instructions, refer to the topic [Event Action Plans and Alarm Instructions for a Macro](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/event-action-plans-and-alarm-instructions-for-a-macro.md) for the procedure.

### Configuring the History / Notes tab

1. Click the **History / Notes** tab, and configure as required.
2. Click the **Save** button to apply your changes.


---

# 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/creating-a-random-selection-item-and-configuring-a-rule.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.
