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

# Challenge

The Command Centre Challenge feature allows an operator to contest Cardholders as they attempt to gain access through a Door. Operators may use the feature to visually confirm the identity of each Cardholder before manually granting access to a secure area. This means that an operator is notified at their Workstation, whenever a Cardholder presents their card at a Door that is being challenged. The operator then has the final determination as to whether a Cardholder is granted or denied access.

The Challenge feature is designed to be an extension of the [*Dual Authorisation*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#dual-authorisation) feature, where an operator working remotely from their Workstation takes on the role of the second Cardholder.

**Notes:**

* Refer to [Operator Privileges](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-privileges.md) to check you have the correct operator privilege level for working with Challenge.
* Ensure the Workstation PC clocks are synchronised with the Command Centre Server to prevent potential timing issues. If the time between a workstation and the server is more than 30 seconds it will fail to work correctly. Also, both server and workstations need to be on the same time zone.

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring Challenge](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/configuring-challenge.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [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)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Challenge Viewer - Controlled Challenge mode](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/challenge-viewer-controlled-challenge-mode.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Challenge Viewer - View-Only mode](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/challenge/challenge-viewer-view-only-mode.md)


---

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