> 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-configuration/configuration-example.md).

# Configuration Example

The Visitor Management Kiosk uses a single operator to act as both the visitor signing in and the host 'logging on' to perform actions.

The following example shows the recommended set up where the system is for a single Company, and the Visitor Management configuration requirement for all Kiosks is the same. At least one Reception must be configured regardless of whether physical Receptions exist or not.

Permanent Cardholders may be treated as visitors when they visit another part of the organisation. In the example below the **Cardholder Division** represents an existing Division (which may be at the top of a hierarchy of Divisions) containing Cardholders who could be visitors. Where there are Cardholders who can act as visit hosts, that are not in any of the 'Find Visitor' Divisions, privileges will be required to view Cardholders in the additional (host) Divisions.

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

**Notes:**

* To allow 'visiting' permanent Cardholders to edit their details, the "Edit Cardholders" privilege must be granted in the (permanent) Cardholder Division.
* It is possible to restrict the information that could be seen/edited using PDF privileges. If the kiosk operator only has the privilege to view Cardholders in these Divisions, their details will be displayed but will not be editable.
* To allow a site to stop permanent Cardholders (on a visit) from editing their details, the kiosk will allow Cardholders in the Find Visitor Divisions to either sign in for an existing visit or to create new visits for themselves with just a view Cardholders privilege. The implication is that there may be visitor fields which have been marked as required when adding to a visit / marking on site that cannot be entered or updated. To allow for this, when the visitor signs in, the screen that presents the visitor details for checking and update will appear read only and all validation around required fields and format will be ignored. Similarly when a visitor in a read only Division is marked on site, any validation around required fields will be ignored.
* The "Manage Visitor attributes" privilege allows the Cardholder to be updated with the last time they read the induction material. This privilege will only be required if induction material has been configured and the operator does not have the "Edit Cardholders" privilege in that Division.
* If it is not possible to put the Kiosk Visitor Type Access Group and all access granting Access Groups in the Save Visitor Division, the "Modify Access Control" privilege will be required in the Divisions in which those Groups are stored AND either the "Edit Cardholders" or a view Cardholders privilege will be required in each of the Divisions containing Cardholders who may be assigned to these Groups.
* Assuming that the kiosk operator has the ability to view the details of the Cardholder badging at the 'Welcome screen', the system will be able to establish whether the Cardholder is a member of any of the Host Type Access Groups for the kiosk visitor type or Tour Group visitor types and therefore a host.

### Recommended Operator Groups

For the setup described it is recommended that at least the first two Operator Groups be created:

<table><thead><tr><th width="120">Operator Group</th><th>Privileges / Divisions</th></tr></thead><tbody><tr><td>Group 1</td><td><p>Visitor Attributes, and either "Edit Cardholders" or view Cardholders in Find Visitor Division.</p><p>If Cardholder Notes have been configured for the kiosk visitor type and are to be displayed/editable via the kiosk, either the "View Cardholder Notes" or "Edit Cardholder Notes" privilege in the Find Visitor Division.</p></td></tr><tr><td>Group 2</td><td><p>"Edit Visits", "Edit Cardholders", "Modify Access Control", and "View Events and Alarms" in the Save Visitor Division.</p><p>If Cardholder Notes have been configured for the kiosk visitor type and are to be editable via the kiosk, the "Edit Cardholder Notes" privilege in the Save Visitor Division.</p></td></tr><tr><td>Group 3</td><td><p>Only applicable if there are hosts in Divisions that have not been configured as Find Visitor Divisions.</p><p>The privilege to view Cardholders in each of the Divisions that could contain a host.</p></td></tr><tr><td>Group 4</td><td><p>Only applicable if any of the access granting Access Groups is not in the Save Visitor Division.</p><p>"Modify Access Control" in the Save Visitor Division.</p></td></tr></tbody></table>

**Note:** If you will be using the Visitor Management client, it is possible that a combination of the Groups created for Receptionists may be used.

See [Configuration Examples](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/configuration-examples.md) (in the 'Visitor Management' section) for suggestions where different configuration is required for different Kiosks or Receptions.


---

# 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-configuration/configuration-example.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.
