> 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-view-only-mode.md).

# Challenge Viewer - View-Only mode

### Introduction

The View-Only Challenge mode allows operators with the “View Challenge” operator privilege to open the Challenge Viewer against the Door (which must be within the operators Division).

The Challenge Viewer opens in View-Only mode, therefore access is granted to the cardholder based on the standard Access Group and Schedule settings without operator intervention.

Any number of Challenge Viewers may be opened against a single Door in **View-Only** mode.

### Procedure

1. Click **Configure** from the menu bar, then **Doors**.
2. **Right click** on the door you wish to challenge access to.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2043f3dda28558e9527606319ddc1f2a87c4d044%2Fcontrolledmode.png?alt=media)
3. Select **View Only Challenge**, then **Entry** or **Exit** as appropriate.

   The Challenge Viewer opens:

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

   The Challenge Viewer displays the Cardholders details and PDFs as defined in the Property pages of the Door being challenged.

   The Challenge Viewer monitors the system for Card related events for the Door being challenged. When an event is received the Viewer determines that it is running in **View Only** mode, therefore there are no **Grant Access** or **Deny Access** buttons available.
4. Click the **Close** button to close the Challenge Viewer.


---

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