> 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/configuring-command-centre/viewer-configuration-overall-process/configuring-tiles/configuring-individual-tile-types/configuring-an-access-decision-tile.md).

# Configuring an Access Decision Tile

This Tile is used to display the Access Decision, as determined by the system in response to an access request, at the entry reader on a designated Door. This Tile is only applicable to the Monitor Site Viewer. When used for *Challenge\**, it is only used in a scenario where the dual authorisation functionality (Controlled Challenge), currently available in Configuration Client is not applicable. The configured door will be a dummy and not monitored.

**Note:** The Door monitored may be a local or remote Door.

{% hint style="info" %}
**\*Challenge**

The Challenge feature allows a Command Centre operator to contest Cardholders as they attempt to gain access through a Door, and either grant or deny access.
{% endhint %}

### How to configure

The only specific configuration for this tile is to select the Door against which the reader to be monitored for access requests, as follows:

1. Double-click on **Access Decision** on the 'Tile Toolbox'.

   The Access Decision Tile appears on the Configuration Panel section of the screen in preview mode.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-92f4291f5741e36090b59f9b6c363906049295c2%2Faccessdecision_previewmode.png?alt=media)
2. Move the mouse over the Access Decision Tile you have added, and click on the **Click to configure** button that appears.

   The Access Decision Tile Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e95dd3d1b61e9cde1143009b6baab04aaffaa19d%2Faccessdecision_tileconfig.png?alt=media)
3. Enter an appropriate **Title** for this tile.
4. Uncheck the **Show Tile Header** checkbox if you want the tile header to be removed in operational mode.

   **Note:** While this feature maximises the available screen real estate, be aware that Tile maximise/minimise can only be achieved using hot keys < **Ctrl** + **M** >.
5. The **Last Cardholder at Door** field allows you to specify the Door whose access decisions will be displayed in the tile. Click the **Select Door** button.

   A browse tool displays.

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

   **Note:** Local and remote Doors are displayed.
6. Check the door you want to use.
7. Click the **OK** button.

   The pop-up closes and the **Select Door** button changes to the name of the door you selected.
8. Click the **Close** button.

   The preview mode of the Access Decision Tile now displays the name of the Door that it has been configured for.

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


---

# 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/configuring-command-centre/viewer-configuration-overall-process/configuring-tiles/configuring-individual-tile-types/configuring-an-access-decision-tile.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.
