> 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-challenge.md).

# Configuring Challenge

### Introduction

Configuration of Challenge is defined in several tabs on the Property pages of Controller Doors. This procedure describes how to configure Challenge for a Door that has already been configured.

Operators must have the "Site Edit" operator privilege to perform this procedure.

**Note:**

Controlled Challenge mode means the Challenge Viewer will open automatically when a Challenge event occurs. There are a number of ways to configure Controlled Challenge for specific operators/workstations, depending on your site requirements. For further instructions, refer to [Configuring Doors for Controlled Challenge mode](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/configuring-doors-for-controlled-challenge-mode.md).

***

### Configuration

To configure Challenge, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Doors**.

   The **Door** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight the door the Challenge feature is to be added to.
3. Right click and select **Properties**.
4. Click each tab in turn and configure Challenge on the door properties as required:

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2d4e2d2bc8ad4676ff39dc7848b5efeddad05762%2Fdoor_advancedtab.png?alt=media)
2. Enter the number (in seconds) in the **Card to complete action must be presented within** field for the time limit an operator is given to grant or deny access. This time limit starts from the time a Cardholder presents their card, and has a range of 1 to 99 seconds.

</details>

<details>

<summary>Challenge tab</summary>

1. Click the **Challenge** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8c9185e198b23d84de8b24282b3bc11d2f117c2f%2Fdoor_challengetab.png?alt=media)
2. The default settings for all Doors in the system are configured in the Challenge and More Challenge tabs of the Server Properties. See [Server Properties](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties.md) for further detail.

   If you want the default settings for this Door to be overridden, then tick the **Set challenge display settings specifically for this Door** checkbox.
3. Tick the checkboxes for the Cardholder fields you wish to be displayed in a Viewer window, (i.e. First Name, Last Name, Description and Card Number).
4. If you require Image based Personal Data Fields to be displayed in a Viewer window, select a **First image field** and a **Second image field** from the drop-down lists.
5. If you require an audio sound to be played whenever a Cardholder challenge occurs, select an **Audio Prompt** from the drop-down list.

   **Note:**

   Wave files used for audio prompts should be less than 5 seconds long.
6. If you require a short explanation from an operator after granting or denying access to each Cardholder, tick the **Operator comment required after each Cardholder Challenge** checkbox.
7. If you require this door to send Challenge events to remote servers, (i.e. in multi-server environments), select the **Enable remote challenge** checkbox.

   With this checkbox selected, Challenge viewers on remote servers will receive challenge events for this door, as well as Challenge viewers on the local server.

</details>

<details>

<summary>More Challenge tab</summary>

1. Click the **More Challenge** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c0e258df0cbde2984d17900c99e7b54cc6cd6aa0%2Fdoor_morechallengetab.png?alt=media)
2. From the list of text and numeric [Personal Data Fields (PDFs](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#pdf-personal-data-field)), select those that you wish to be displayed in a Viewer window by checking the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-78b6786245dd04fd957b81f18dc7f94a341bcae6%2Ftickbox.png?alt=media) tick-box beside the PDFs.
3. Configure a simple font style against each selected PDF.
4. Sort your selection of PDFs by using the **arrow** buttons to the right of the list box if required.

   The order you define will be retained when information is shown in the Challenge Viewer.

</details>

5. Click the **OK** button to save your changes to the Door.
6. Set up a new Access Group (see [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for the procedure).

   **Note:**

   Name the Access Group something meaningful, (e.g. Operator Challenge Group).

   This Access Group will be used for the Dual Authorisation Second Card in Step 24 and should not have any cardholder members. If there are cardholder members, the following message will display when an operator challenges a cardholder using the "Controlled Challenge" mode.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-969dfa91c524fcc0b41ef76462255b3bd9d2db0d%2Fdualauth_message.png?alt=media)
7. Click the **Entry Zone** tab of the Door to see the Door's entry Access Zone, and open the property pages for that Access Zone.
8. Click the **Access Mode** tab.
9. Select an appropriate **Schedule** that is in Dual-Authorisation mode, from the drop-down list.
10. Click the **Dual Authorisation** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2ffcd19af0842d43d66f438c2d4e063abceb7fdf%2Fdualauthtab.png?alt=media)
11. Select an Access Group from the drop-down list for the **First Card**, or leave blank if all cardholders are authorised to access the Door.
12. Select the new Access Group you configured at Step 18, from the drop-down list for the **Second Card**.

    **Note:**

    By setting the Access Group for the Second Card only, the cardholder of the first card presented can be from any Access Group, but the operator will be taking on the role of the second cardholder. This prevents a pair of cardholders from accessing a challenged Door as a normal Dual-Authorisation Door.
13. Click the **OK** button to save your changes to the Access Zone.

### Result

Challenge has been configured for a Door.

Refer to [Opening the Challenge Viewer](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/challenge-viewer-controlled-challenge-mode.md) for the operation of Challenge.

***

### Hint

{% hint style="info" %}
Challenge mode cannot be used in conjunction with 'Double card override' and 'Visitor/Escort' modes.
{% endhint %}


---

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