> 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/command-centre-client/using-command-centre/working-with-viewers/controlled-challenge-viewer/granting-denying-access.md).

# Granting/Denying Access

This procedure describes how to grant or deny access to a Cardholder from the Controlled Challenge Viewer.

1. Click on the row of the Challenge event you want to make an access decision for, so it becomes highlighted.

   **Note:** Either the Panel configured specifically for the Door for which the event was generated, or the default Panel will display. Any Cardholder Tiles are not editable from this Viewer.
2. 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, (i.e. the time indicated in the "Seconds Remaining" column), the cardholder is denied access.

   If you chose to deny access and the **Operator comment required after each Cardholder Challenge** option has been enabled in Configuration Client, (either on the Challenge tab of the Server Properties or for the Door) the Challenge Decision pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-906d27c553820d1f104444a12a0f56bdbbe891ce%2Fchallengedecisionpopup.png?alt=media)

   Enter a short reason why access has been denied.
3. Click the **OK** button.

   Regardless of the decision, the event is cleared from the list, the number of Challenge events waiting decreased by one, the next event selected automatically, and the appropriate panel displayed. If there are no more events in the Navigation Panel, the Panel area will be cleared, and the Grant/Deny buttons disabled.


---

# 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/command-centre-client/using-command-centre/working-with-viewers/controlled-challenge-viewer/granting-denying-access.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.
