> 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.md).

# Visitor Management Kiosk

### Introduction

The Visitor Management Kiosk, which is a licensable feature, allows visitors to a site to register their details from a self-service touch screen kiosk, and to automatically notify the host of the visitor's arrival without intervention by a reception. Hosts retain the responsibility for meeting the visitors and marking them on or off site, to ensure evacuation reports are up to date at any time.

The Visitor Management Kiosk supports:

* **Individual visitors** arriving for a visit, who may or may not be pre-registered by the host.
* **Tour Groups** which have been pre-registered by the host. All members of a Tour Group must arrive and leave together.
* **Rapid Entry**, where existing cardholders who belong to specific Access Groups can use the 'Fast Track" process to gain quick entry.

The following general functionality is included to support the Visitor Management Kiosk:

* Automated logon (also known as 'single sign on') for hosts to the Gallagher Visitor Management client (this is the main client, not the kiosk) using the host's Windows logon credentials. This will allow hosts to pre-register visits. Command Centre configuration is required for each host to allow single sign on to the Visitor Management client.
* A Click-once installer to allow for installation of the Visitor Management Kiosk software.
* Visitor records are stored within the Command Centre database and their details can be viewed, updated or reported on from Command Centre.
* Configuration required for the kiosk, including configuration of the operator logon credentials for the kiosk will be achieved via Command Centre.
* A touch screen Visitor Management Kiosk. See [Visitor Management Kiosk screens](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens.md) for further detail on the screens that a self service kiosk provides.

The following features can be configured:

* Cards can be assigned to single visitors.
* Visitors can scan their business cards at a kiosk to simplify and speed up the data entry process.
* Capturing images.
* Support for Tour Groups.

***

### Licensing

Visitor Management Kiosk is a licensable feature. The license file must contain the following options:

<table><thead><tr><th width="198">License option</th><th>Description</th></tr></thead><tbody><tr><td><code>[Features]</code><br><code>VisitorManagement=1</code></td><td>Allows you to see and configure the Kiosk in Configuration Client on the Division setup.</td></tr><tr><td><code>[Limits]</code><br><code>Visit Kiosk=X</code></td><td>The number <code>X</code> indicates how many Kiosk Clients can be connected at one time.</td></tr></tbody></table>

In addition to these two options, if you want Hosts to be automatically notified of their visitor's arrival, your site licence file must also contain the option:

`[Features]`\
`Notifications=1`

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Visitor Management Kiosk Installation Instructions](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-installation-instructions.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Visitor Management Kiosk Configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-configuration.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring Visitor Management Kiosk](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/configuring-visitor-management-kiosk.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Visitor Management Kiosk Document Scanning Process](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-document-scanning-process.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Visitor Management Kiosk screens](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management-kiosk/visitor-management-kiosk-screens.md)


---

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