> 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/command-centre-site-configuration/configuring-visitor-management-setup/visitor-fields-on-visit-tab.md).

# Visitor Fields on Visit tab

This tab allows you to configure what columns will appear on the **Visit** screen for a particular Visitor Type, in the Visitor Management application.

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

The Visitor Type(s) that you dragged and dropped onto the **Visitor Types** tab appear in the Visitor Type grid on this screen.

1. Select the Visitor Type you want to select the visitor fields for.

   The visitor fields are a combination of some mandatory fields, (e.g. Visitor **Name** ), and Personal Data Fields (PDFs) that are assigned to the Visitor Type, (i.e. Visitor Type Access Group).

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

   The ‘Available Fields’ and ‘Selected Fields’ grids become enabled.

   The ‘Available Fields’ grid is populated with the fields which are available to display for each visitor on the **Visit** screen in the Visitor Management application, but have not been selected.

   The ‘Selected Fields’ grid is populated with the mandatory fields, (e.g. **Name** is always in the 'Selected Fields' list), and cannot be removed.
2. Move any of the fields you require from the ‘Available Fields’ grid to the ‘Selected Fields’ grid by selecting the field 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.

   **Note:** If "Card Number" is selected, a read-only **Card Number** column (which can be sorted on), showing cards assigned to visitors, will appear on the Visit screen.
3. Once you have all the fields you require in the ‘Selected Fields’ grid, you can re-order the fields if required by using the **up** and **down** arrow buttons to the right of the ‘Selected Fields’ grid.

   **Note:** The order you sort these fields in here will be the order they appear in the Visitor Management application.


---

# 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/command-centre-site-configuration/configuring-visitor-management-setup/visitor-fields-on-visit-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.
