> 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/viewing-visits-in-command-centre.md).

# Viewing Visits in Command Centre

### Introduction

When visits have been created in the Visitor Management application, their details can be viewed in Command Centre by using the Find tool and searching for visits. However, visits are not available from a List Window, like most Command Centre Items.

**Note:** Visits cannot be included in macros, or appear on Site Plans.

### Operator Privileges

“View Visits” is required to view a Visit's properties.

### Procedure

1. Click **Monitor** from the menu bar.
2. Click **Find…** to open the Find window.
3. Click the "Look In" field and select the option **Visit**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-eddf7b28ccf6301cb6043ff43742a02cec08fbe6%2Fvisit_findtool.png?alt=media)
4. Click the **Related To** tab.

   The **Related To** tab searches for items in the "Look In" field on the **General** tab that are related to the item in this window.
5. Open the **Division** List Window.
6. Select the relevant Division(s) and drag and drop it into the "Related To" window.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-af3a54c3b5c1231a202eb8d612c149deb5220179%2Fvisit_findtool2.png?alt=media)
7. Click the **Start Search** button.

   The Search window opens and displays all those pre-registered Visit(s) that are related to the Division(s) selected.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6c851d361cb1da9e9a68f4353da0fde778bf5cb4%2Fvisit_findsearch.png?alt=media)
8. Double-click on the Visit you want to look at the details of.

   The **General** tab of the Visit property pages displays.

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

   All the fields on this screen are "read-only".
9. Click the **Details** tab.

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

   All the fields on this screen are "read-only".
10. Click the **Meeting With** tab.

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

    All the fields on this screen are "read-only". There are three columns of information:

    * Meeting With
    * Start Time
    * End Time
11. Click the **Visitors** tab.

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

    All the fields on this screen are "read-only". There are eight columns of information:

    <table><thead><tr><th width="162">Column</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>The name of the visitor.</td></tr><tr><td>Status</td><td><p>The visitor's status for this visit. Available statuses are:</p><ul><li>Expected</li><li>On-Site</li><li>Expected Back</li><li>Departed</li><li>Cancelled</li></ul></td></tr><tr><td>Alarm State</td><td><p>The visitor's alarm state for this visit. Available alarm states are:</p><ul><li>Ok</li><li>Due to Leave</li><li>Over Due</li></ul></td></tr><tr><td>Card Issued</td><td><p>Available options for this column are:</p><ul><li><p><strong>[Card Type Name] [card number]</strong></p><p>This displays if a card has been issued to the visitor.</p></li><li><strong>No Card allocated</strong><br>This displays if a card has not been issued to the visitor.</li></ul></td></tr><tr><td>Access Groups</td><td>A comma separated list of the names of Access Groups that have been assigned to the visitor as part of the “Mark On-site” action.</td></tr><tr><td>Actions</td><td><p>A comma separated list of the names of actions that have been performed for this visitor. Action names are:</p><ul><li>Print Badge</li><li>Assign Card</li><li>Mark On-Site</li><li>Temp Off-Site</li><li>Leave Site</li></ul></td></tr><tr><td>On Site At</td><td>The actual time the visitor was marked as “On-site”.</td></tr><tr><td>Left Site At</td><td>The actual time the visitor was marked as “Left Site”.</td></tr></tbody></table>
12. Click the **Notes** tab.

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

    If any "Notes" were entered in the Visitor Management application for this visit, they will appear on this screen. However, unlike the other tabs, this screen is **not** "read-only", (i.e. you can add a note(s) about this Visit if required).

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).


---

# 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/viewing-visits-in-command-centre.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.
