> 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/configuration-client/site-installation/doors/challenge/configuring-doors-for-controlled-challenge-mode.md).

# Configuring Doors for Controlled Challenge mode

### Introduction

There are a number of scenarios surrounding how Controlled Challenge can be configured for specific operators/workstations, depending on your site requirements. Below are some possible scenarios, each with configuration instructions to ensure Controlled Challenge works as required.

#### Scenario 1:

An operator is required to operate Controlled Challenge for a Door(s) and is NOT allowed to “turn it off”.

**How to configure:**

To do this, the administrator will need to ensure that EITHER:

* The operator is NOT privileged to change the System View, OR
* The operator does not belong to any Operator Group that does NOT have the Controlled Challenge privilege for that Door.

#### Scenario 2:

An operator is allowed to choose whether or not they will monitor/operate Controlled Challenge for a Door(s).

**How to configure:**

This is possible using System Views. To do this, the administrator will need to ensure that:

* The operator is privileged to change the System View, AND
* The operator belongs to an Operator Group that has the Controlled Challenge privilege for the Door(s), AND
* The operator also belongs to an Operator Group that does NOT have the Controlled Challenge privilege for that Door.

#### Scenario 3:

Two operators, working at separate workstations, are required to monitor and/or operate Controlled Challenge for the same Door(s) at the same time.

**How to configure:**

This is done by putting both operators into an Operator Group which has the Controlled Challenge privilege for the Door(s). In this scenario, for event Challenge Event, access is controlled by the first operator to grant or deny access.

#### Scenario 4:

One operator is required to operate Controlled Challenge for a Door(s) while another operator is required to operate Controlled Challenge for a different Door(s).

**How to configure:**

This is done by putting the operators into separate Operator Groups which each have the Controlled Challenge privilege for the appropriate Doors.

#### Scenario 5:

An operator is required to operate Controlled Challenge for a Door(s) when they are logged onto one workstation but not when they are logged onto another workstation.

**How to configure:**

To do this, an administrator would need to set up Workstation Operator Groups appropriately.

#### Scenario 6:

At one workstation, an operator is required to operate Controlled Challenge for a Door(s) and must NOT be allowed to “turn it off”. At another workstation the same operator is allowed to choose whether or not they will monitor/operate Controlled Challenge for that Door(s).

**How to configure:**

This is possible by using Workstation Operator Groups to prevent the System View from being changed on one workstation but not the other.

#### Scenario 7:

Morpho biometric readers are being used at doors that have been configured for Controlled Challenge, and are required to provide feedback in a challenge situation. However, Morpho biometric readers do not normally provide feedback in a challenge situation, (i.e. although the fingerprint/vein is accepted, there is no feedback that access has been granted through the door), therefore indicator lights are used to provide feedback.

**How to configure:**

Feedback using indicator lights at Morpho biometric readers can be achieved, as follows:

1. Create a new output for each indicator light, (i.e. *"Wait Sign"*, *"Access Granted"* and *"Access Denied"*).
2. Create a new virtual output, (i.e. *"Card Presented Event"*).
3. Create two new Macros, (i.e. " *Access Denied Sign Relay"* and *"Card Presented Event"*).
4. Create the following two new Action Plans", and ensure the **Alarm Priority** is set to "Message Only" for both:

   * *"Access Denied Card Event"*.

   On the **Disarmed** tab, drag and drop the "Access Denied Sign Relay" macro to run from this Action Plan into the **Cameras, Macros, and External System Items** grid.

   * *"First card presented event"*.

   On the **Disarmed** tab, drag and drop the "Card Presented Event" macro to run from this Action Plan into the **Cameras, Macros, and External System Items** grid.
5. Create the Challenge Controlled door. On the **Event Response** tab:
   1. Select the "Access Denied" Event Group and assign the "Access Denied Card Event" Action Plan.
   2. Select the "Card Event" Event Group and assign the "First card presented event" Action Plan.
6. Create the following two new Logic Blocks to control the indicator lights:

   * *"Reset Wait Sign"*.

   On the **Rules** tab, add the following **Logic items**; "Access Granted" output, "Access Denied" output and "Door Open Switch" input.

   On the **Timing** tab, set the **Delayed off time** to 3 seconds.

   * *"Wait Sign"*.

   On the **Rules** tab, add the following logic items; "Card Presented Event" virtual output and "Reset Wait Sign" logic block.

   On the **Timing** tab, set the logic block to be latched on until cleared by the "Reset Wait Sign" logic block.


---

# 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/configuration-client/site-installation/doors/challenge/configuring-doors-for-controlled-challenge-mode.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.
