> 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/configuring-visitor-management-kiosk/configuring-visitor-management-for-the-kiosk/kiosk-host-fields-tab.md).

# Kiosk Host Fields tab

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

This tab is used to define the Host fields that will be used when a visitor searches for a host (on the 'Who are you meeting with? screen' of the Kiosk), and will appear on the 'You are signed in screen' of the Kiosk.

**Note:** There is no limit to the number of items you can select.

1. Move any of the fields you require from the 'Available Fields' grid to the 'Selected Fields' grid by selecting the PDF and clicking the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-02f3fa34a8c66e754c2afaa04f6b33c637a8d0a9%2Frightarrow.png?alt=media) button.

   **Notes:**

   * Host fields that display contact information are recommended, (e.g. email, phone number, mobile), as well as departmental information so that a visitor can verify the correct Host.
   * The 'Available Fields' grid displays all non-image PDFs that the operator is privileged to view.
   * First and Last Name are configured by default and cannot be removed.
2. Once you have all the PDFs you require in the 'Selected Fields' grid, you can re-order them if required by using the **up** and **down** arrow buttons to the right of the 'Selected Fields' grid.


---

# 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/configuring-visitor-management-kiosk/configuring-visitor-management-for-the-kiosk/kiosk-host-fields-tab.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.
