> 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/products/cc-software/operate/visitor-management-client/pre-registration-and-receptionist-functions/the-visit-screen.md).

# The Visit screen

### Description

The Visit screen enables you to create, edit, copy, cancel, restore and view a visit. This screen displays details about the visit and lists each visitor on the visit.

**Notes:**

* If you are a Pre-registration user, this screen displays automatically at logon.
* Pre-registration users require the "Edit Visits" operator privilege to create and edit visits.

To open the Visit screen either:

* click the **Visit** button located on the toolbar (which creates a new visit), or
* double click a visitor record, or
* click the visit icon ![](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f878c6ba2892234dbd673f35052f930dca071c0f%2Fvm_visiticon.jpg?alt=media)

### The Visit screen

![](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3e911aa4bc64cba6edeed6b31a5d76f19f267c69%2Fvm_visit_screen.png?alt=media)

The Visit screen displays your default reception, the columns and action buttons (if applicable) for this reception, as configured in Command Centre.

### Fields on the Visit screen

This table describes the mandatory (\*) fields on the Visit screen.

<table><thead><tr><th width="132">Field</th><th>Description</th></tr></thead><tbody><tr><td>Reception</td><td>This drop down is populated with a list of receptions you can edit or view visits for. The reception selected determines if the Badge Text and Access fields are displayed.</td></tr><tr><td>Visitor Type</td><td>This drop down is populated with a list of visitor types valid for the selected reception.</td></tr><tr><td>Meeting With</td><td>This drop down is populated with a list of cardholders who can host visits for the selected visitor type for this reception (once you have started typing a value into the field).</td></tr><tr><td>Arriving</td><td>This is the planned start date and time for the visit.<br><br><strong>Note:</strong> This field defaults to the current date and time.</td></tr><tr><td>Departing</td><td>This is the planned end date and time for the visit.<br><br><strong>Note:</strong> The date defaults to the current date. The time defaults to the standard end of day time. If the visit is created after the standard end of day time and before the standard start of day time on the following day, the time will default to 1 hour after the arriving time.</td></tr></tbody></table>

This table describes the non-mandatory fields on the Visit screen.

<table><thead><tr><th width="132">Field</th><th>Description</th></tr></thead><tbody><tr><td>Purpose</td><td>Enter a purpose for the visit.</td></tr><tr><td>Location</td><td>Enter a free text location for the visit.</td></tr><tr><td>Badge Text</td><td>This field will only appear if configured in Command Centre. This field enables you to select text to be printed on the visitor's badge.</td></tr><tr><td>Access</td><td>This field will only appear if configured in Command Centre. This field enables you to specify what access will be given to the visitors on this visit when they are marked on-site.</td></tr><tr><td>Notes</td><td>Enter a note for the visit.</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/products/cc-software/operate/visitor-management-client/pre-registration-and-receptionist-functions/the-visit-screen.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.