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

# Visitor Fields tab

This tab allows you to configure what will appear on the **Visitor** screen for each 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-a5099408b6986852ee564902711fc214783f9139%2Fdivision_visitorfields_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 **First Name** and **Last 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-8c42ea6d4ff7b1f6ed55331551c4a136df95d3ce%2Fdivision_visitorfields_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 on the **Visitor** screen in the Visitor Management application, but have not been selected.

   The ‘Selected Fields’ grid is populated with the mandatory fields, (e.g. **First Name** and **Last Name**, are always in the 'Selected Fields' list), and cannot be removed.

   **Note:** If you click on either the **First Name** or **Last Name** fields the options in the 'Selected Field' section change as shown. The options available in the drop-down are 'Either First or Last Name' or 'Both First and Last Name'.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c63c30b3b99a6a1d0a2f69d2bca259197a3186f1%2Fselectedfields_checkboxes2.png?alt=media)
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** field, showing cards assigned to visitors, will appear on the Visitor window.
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.
4. By clicking on a field in the ‘Selected Fields’ grid, the checkboxes below become enabled.

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

   If you click on a **PDF** in the 'Selected Field' grid, an additional **Include in Automatic notifications** checkbox displays.

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

   **Note:** If you have moved **Escort** to the 'Selected Fields' grid, and click on it, all the checkboxes are disabled.
5. Check the required checkbox(es) for each selected field as appropriate.

   <table><thead><tr><th width="228">Checkbox</th><th>Checking this means...</th></tr></thead><tbody><tr><td>Required when adding to a visit</td><td><p>the value of the field must be entered at the time you add a visitor to a visit.</p><p><strong>Notes:</strong></p><ul><li>Checking this control disables the "Required when marking On Site" control. You get the mandatory On Site automatically.</li><li>Any PDFs with the 'Required Field' ticked (on the <strong>Type</strong> tab) must have 'Required when adding to a visit' here checked also.</li></ul></td></tr><tr><td>Required when marking On Site</td><td><p>that the value of the field does not have to be entered until the visitor is on site, (e.g. a photo of the visitor would usually not be able to be taken until the visitor arrives on site).</p><p>This is only mandatory before marking On Site.</p></td></tr><tr><td>Remember when creating visitors</td><td>the system will remember the value of the field for each visitor, (e.g. if all visitors on a visit are from the same Company, this option saves re-entering the Company name for each visitor).</td></tr><tr><td>Include in Automatic notifications</td><td><p>that the PDF will be included in automatic arrival and departure overdue notifications sent to hosts/escorts.</p><p><strong>Notes:</strong></p><ul><li>Departure notifications are managed by the server and privileges cannot be applied to them. Therefore, if you have sensitive data in these PDF's do not configure departure overdue notifications, or do not include these PDF's as Automatic Notifications.</li><li>This option will be disabled for Image PDFs.</li></ul></td></tr></tbody></table>


---

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