> 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/visitor-management-barcode-scanner-process.md).

# Visitor Management Barcode Scanner Process

### Introduction

Visitors can be assigned a QR Code barcode (Quick Response Code format), to allow them to sign in and sign out as fast as possible.

### Prerequisites

In order for the Visitor Management Client and Kiosk to use barcodes to sign visitors in or sign out, additional software must be installed on any workstation that runs the Visitor Management Client or Kiosk.

See [Software required for Barcode Scanner Support](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/visitor-management-barcode-scanner-process/software-required-for-barcode-scanner-support.md) for details.

### Procedure

#### Creating a Badge with barcode

1. Create a visitor card/badge with barcodes in Configuration Client.

   See [Adding Visitor details to cards/badges](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/adding-visitor-details-to-cards-badges.md) for the procedure.

#### Setting up email for sending invitation

Configure email in Configuration Client so the Reception is able to send an email from Visitor Management.

2. Set the site default mail user agent, as follows:
   1. Click **File** from the menu bar, then **Server Properties**.
   2. Click the **Advanced** tab.
   3. Select the appropriate **Site Default Mail User Agent** from the drop-down list.
3. Set the email programme to use for sending invitations to Visitors during the Hosts Visit creation and edit process, as follows:
   1. Open the default Reception for the Workstation.
   2. Click the **Visitor Management** tab.
   3. Click the appropriate **Mail User Agent** radio button for the mail programme you want to use to access the email software.

      **Note:** If the option you select is not available when invoked, the ‘Default Mail User Agent’ (configured on the **Operator Defaults** tab of the Server Properties) will be used.

#### Enabling the Send Invitation action for Receptionists

Allow Receptionists to send invitations in Configuration Client.

4. Click **Configure** from the menu bar, then **Divisions**.

   The Division List Window opens.
5. Open the "Visitor Division", (i.e. the Visitor Management Configuration Division), and click the **Visitor Management** tab.

   The **Visitor Types** sub-tab displays by default.
6. Click the **Reception Actions** sub-tab.
7. Check the **Send Invitation** checkbox.
8. Click the **OK** button to exit and save your changes.

#### Creating an Invitation

Create an invitation in the Visitor Management application.

9. From either the Visit or Home screen, select a visitor record and click the **Invite** action button.

   **Note:** This requires the Visitor to be the correct Visitor Type and have a configured Email PDF with a valid Email in it. If not, an email will still be created but the To field will be blank.

   The Visitor receives the email with an attached **.png** file containing the QR Code barcode.

#### Visitor Arrival

When the Visitor arrives for the visit:

* they can scan the Barcode directly from the cell phone or printed out on a piece of paper, this will either mark them as signed in or on site depending on configuration.
* a Badge is printed that contains a Barcode (this is a manual action).
* when the Visitor is ready to leave, they swipe the Barcode on their Badge and they are marked off site.


---

# 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/visitor-management-barcode-scanner-process.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.
