> 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/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens.md).

# Visitor Management Kiosk screens

The screens that appear on a self service Visitor Management Kiosk, and the order they appear in, are as follows:

### Initialisation screen

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

When the Visitor Kiosk application is launched either the 'Logon screen' displays or logon occurs automatically if the Kiosk's Windows user account is configured for Active Directory single sign-on within Command Centre.

**Note:** If either 'Personal Document Scan' or 'Contact Document Scan' option are enabled, the Visitor Kiosk will check for the scanner and associated SDK. If the Visitor Kiosk cannot detect them, the following message will appear on the ‘Initialisation screen’, and the operator will not be allowed to logon:

*"Failed to initialise Acuant Scanner. Ensure the Acuant SDK has been installed correctly and the scanned is connected to the workstation."*

Check the scanner connection and install the SDK before starting the Visitor Management Kiosk application.

### Welcome screen

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

The 'Welcome screen' is the default screen for the Kiosk and the screen returned to after visitor sign-in or other processes at the Kiosk have completed. It is the screen that is returned to whenever a process is cancelled, or if the Kiosk has been inactive for a predetermined time.

The screens that follow depend on what start option button you select.

**Note:** The screen shot above shows the default names of the start option buttons, however the text on these buttons may differ as they are configurable in Command Centre. Also, the 'Visitor Sign Out', 'Tour Group' and 'Staff' buttons will only appear if configured to do so.

[Visitor Sign In](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens/visitor-sign-in.md)

[Visitor Sign Out](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens/visitor-sign-out.md)

[Tour Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens/tour-group.md)

[Staff](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens/staff-rapid-entry.md)

### Host Actions

A Host can log on at the Kiosk when the 'Welcome screen' is displayed, by badging their card at the reader. See [Host Actions](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens/host-actions.md) for sample screens.


---

# 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/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens.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.
