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

# Visit Configuration tab

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

Configure as appropriate:

<table><thead><tr><th width="234">Field / Button</th><th>Description</th></tr></thead><tbody><tr><td>Start Time</td><td><p>This is the standard start of day time.</p><p>(Default = 9:00am)</p></td></tr><tr><td>End Time</td><td><p>This is the standard end of day time, and is used to set a default departing time for the visit.</p><p>(Default = 5:00pm)</p></td></tr><tr><td>Find Visitors in these Divisions</td><td><p>The division(s) from which the list of available visitors for a visit will be built. For a simple site setup this will be the Cardholder Division(s).</p><p>(Default = The name of the division being configured and can be changed to any other division you have the ability to see.)</p></td></tr><tr><td>Save Visitors in this Division</td><td><p>The division in which visits and visitors for that reception will be created. This will be the Visitor Division.</p><p>(Default = The name of the division being configured and can be changed to any other division you have the ability to see.)</p></td></tr><tr><td>Badge Text</td><td>You can specify a list of items which can then be selected for a visit and printed on a badge. You can type in the actual text that you want to appear on visitor badges or copy items in, clicking the <strong>Add</strong> button after each line of text, (e.g. a "VIP" badge marking, or an area the visitor is allowed to visit).</td></tr><tr><td>Visitors are marked as</td><td>Check the appropriate radio button for how you want Visitors to be marked as on arrival, (i.e. either <strong>Signed In</strong> or <strong>On Site</strong>).</td></tr><tr><td>Tour Groups are marked as</td><td>Check the appropriate radio button for how you want Tour Groups to be marked as on arrival, (i.e. either <strong>Signed In</strong> or <strong>On Site</strong>).</td></tr><tr><td>Automatic Arrival Notification</td><td><p>Check this option if you want a notification to be automatically sent to the Host/Escort(s) when the Receptionist chooses the 'Sign In' action, when a visitor arrives on site, and then click the appropriate radio button.</p><p><strong>Notes:</strong></p><ul><li>This setting applies to both the Visitor Management client and Visitor Management Kiosk.</li><li>A Host/Escort is the person a visitor is meeting with.</li><li>Clicking the <strong>Notify Host/Escort for the first visitor only</strong> radio button means that the host will only be sent one notification when the first visitor in a Visit arrives, rather than them receiving notifications for every member of a Visit.</li></ul></td></tr><tr><td>Automatically reschedule late visits</td><td><p>Check this option if you want late visits to be automatically rescheduled. When enabled, if a visitor arrives for a visit after the visit is scheduled to start the system will change the scheduled start and end time for the visit, so that the visitor’s visit is still for the same length of time, e.g.</p><p>A visit is scheduled to start at 2:00pm and end at 3:30pm.</p><p>The visitor arrives, (i.e. is marked on-site) at 2:10pm.</p><p>The visit is automatically updated to start at 2:10pm and end at 3:40pm</p></td></tr><tr><td>Cancel visits if visitors do not arrive</td><td>Check this checkbox and enter a time in hours and/or minutes, if you want to specify a grace time, after which if a visitor has not arrived, their visit will be cancelled.</td></tr><tr><td>Notify Host/Escort when visitor is overdue</td><td>Check this option if you want a notification to be automatically sent to the Host/Escort(s), (i.e. the person a visitor is meeting with), when a visitor becomes overdue.</td></tr><tr><td>Automatically expire overdue visitor cards</td><td>Check this option if you want overdue visitor cards to be automatically expired. When enabled, a cards expiry time becomes the expected departure time for the visitor plus the departure grace period.</td></tr><tr><td>Visitor departure grace period</td><td><p>A grace period can be specified allowing a visitor extra time on site if their visit goes over the expected length. If a grace period is not required, this can be set to 0.</p><p>(Default = 30 minutes)</p><p><strong>Notes:</strong></p><ul><li>In the Visitor Management application, once a visitor goes past their expected visit <strong>End Time</strong> plus the "Grace Period", the visitors status changes to “Overdue” on the <strong>Home</strong> screen, they appear in the <strong>Exceptions</strong> tab, and an alarm is raised.</li><li>If the grace period is changed in Command Centre, it will not update visits already created, unless the visit end time is edited.</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/visit-configuration-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.
