> 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/server-properties/challenge-and-more-challenge.md).

# Challenge and More Challenge

### Introduction

The Command Centre Challenge feature allows you to contest Cardholders as they attempt to gain access through a Door. You may use the feature to visually confirm the identity of each Cardholder before manually granting access to a secure area.

These two tabs enable you to configure the site wide default settings for the Challenge feature. These settings can be overridden for individual Doors as required. See [Configuring Challenge](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/configuring-challenge.md) for details.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Challenge** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9292e171b317471c0b2697efd396fd0f1567e8a8%2Fchallenge.png?alt=media)
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** form the drop-down list.
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 server’s Challenge Doors 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 server’s Challenge Doors, as well as Challenge viewers on the local server.
8. Click the **More Challenge** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5589da19005a1cd416770a275d355cd0c83f23ad%2Fmorechallenge.png?alt=media)
9. From the list of text and numeric Personal Data Fields (PDFs), 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.
10. Configure a simple font style against each selected PDF.
11. 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.
12. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.


---

# 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/server-properties/challenge-and-more-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.
