> 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/using-visitor-management/receptionist-functions/performing-visitor-actions/printing-a-badge.md).

# Printing a badge

### Introduction

A badge is a printed label given to a visitor which displays information about the visitor and/or visit.

A badge can be used to identify who a visitor is and where a visitor is allowed to be on-site (access area/badge text).

A badge label can be printed in advance or when a visitor arrives. It is recommended that the badge be printed as a self adhesive sticker and attached to a visitor's garment, lapel or tag.

### What information can the badge display?

A badge can display the following information:

* **Visitor Details** (e.g. visitor name, company name, photograph)
* **Visit Details** (e.g. the person they are meeting with, visit arriving date and time, visit departing date and time)
* **Visitor Type** (e.g. contractor, supplier)

  The visitor type controls what information is displayed on the badge and the appearance of the badge, (e.g. a contractor's badge may have a different layout compared to a supplier's badge).
* **Badge Text** (e.g. area of access)

  Badge Text is a piece of text added to the badge. A list of Badge Text options is configured in Command Centre. Select a Badge Text option when you create a visit.
* **Group Name**

  Group Name is the name of the Tour Group, (e.g. the organisation the group is from).
* **Barcode**
* **QR Code**

### Examples

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1807e89ee46d011e03f92f6c60582d05d4a1deb0%2Fvm_badge1small.gif?alt=media) ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b28ebf7eea6d0df594c489253c20199a11a967d0%2Fvm_badge2small.gif?alt=media)

### Recommended printer

The recommended printer is the Dymo LabelWriter 400.

When printing a badge for the first time, the system will prompt you to select a printer. The printer selected will then become the default printer for all subsequent print requests. To change the default printer, select a visitor record and click **Alt+P**. The Print window displays. Select an alternative printer.

**Note:** A different default printer can be set for each reception.

### Procedure

To print a badge, complete the following procedure:

1. Select a visitor record.

   **Note:** Multiple records can be selected.
2. Click the **Print Badge** action button.

   **Note:** The reception configuration determines if the Print Badge action is displayed, or not.
3. The badge label is printed. A message on the status bar shows how many badges were successfully printed out of the number of records which were selected.

   **Note:** The visitor row will be updated to show the next available action.


---

# 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/using-visitor-management/receptionist-functions/performing-visitor-actions/printing-a-badge.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.
