> 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/challenge-viewer-controlled-challenge-mode.md).

# Challenge Viewer - Controlled Challenge mode

### Introduction

When a Door is in Controlled Challenge mode the Challenge Viewer opens automatically for an operator when:

* One of the Door's Access Zones is configured for Controlled Challenge functionality using Dual Authorisation, AND
* The operator has the following operator privileges for the Door (which must be within the operators Division):
  * "View Events and Alarms" and
  * "Controlled Challenge"

The Challenge Viewer pops to the front whenever a Controlled Challenge Event requires processing at a workstation, and the operator makes the final decision as to whether access is granted or denied.

The Controlled Challenge Viewer opens automatically, as long as there are no other Challenge Viewers in Controlled Challenge mode open for this specific Door across all workstations.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5cd0461cd446f8d296f3b46a275d9b5b4bd3b12c%2Fchallengeviewer_dvr.png?alt=media)

This Viewer monitors the system for Card related events for the Door being challenged. When an event is received the Viewer determines what operator action is required based on the event type, the Viewer mode and the Schedule associated with the Door's entry or exit Access Zone.

The Controlled Challenge Viewer displays the following:

* Cardholders details and PDFs as defined in the Property pages of the Door being challenged.
* The 'Time Remaining', which is the number of seconds left before the current Challenge event will time out (at which point the cardholder will be denied access).
* At any one time, only the most outstanding event will be visible and available for processing. However, all Controlled Challenge Events will be queued in this Viewer in the order in which they were raised, and it provides an indication of how many other events are waiting in the queue. If a queued Challenge event times out, then this number will update to display the correct queue count.

Only one Challenge Viewer across all Workstations may be opened in **Controlled** mode per entry and exit side of each Door.

### Procedure

1. Decide whether to grant or deny access to the Cardholder, and click the **Grant Access** or **Deny Access** button as appropriate.

   **Note:**

   If you fail to grant or deny access within the time specified on the **Advanced** property tab of the Door, the cardholder will be denied access.

   If the **Operator comment required after each Cardholder Challenge** checkbox is ticked in the Door Properties, then another window will display.
2. Enter a short comment.

   The comment is limited to 256 characters and is stored in an operator event in the system.

   **Note:**

   Even if an operator comment is not required, an event is still generated. The event includes the following:

   * Whether access was granted or denied
   * Date and time access was granted or denied
   * The Door at which the Challenge occurred
   * The names of the operator that challenged the cardholder, and the cardholder who was challenged
   * The card number presented at the Door.
3. Click the **OK** button.


---

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