> 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/tile-actions/access-decision-tile-actions.md).

# Access Decision Tile actions

If this Tile is viewed, prior to the first person EVER requesting access at the reader, the Tile will show the door it is configured for and the message *"No content to display"*.

Whenever a card is badged or a finger is presented at the reader (whichever is applicable) on the configured door, the Tile will display either:

* the message *"Access Granted on dd/mm/yyyy hh:mm:ss"*, and an Access Granted Icon.
* the message *"Access Denied on dd/mm/yyyy hh:mm:ss"*, and an Access Denied Icon.

### Operator Privileges

To View the content of the Tile you need one of the following privileges in the division of the door for which the Tile is configured:

* "View Site"
* "Edit Site"
* "Override Open Door"
* "View Challenge"
* "Controlled Challenge"


---

# 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/tile-actions/access-decision-tile-actions.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.
