> 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/setting-default-receptions-for-workstations.md).

# Setting default Receptions for Workstations

### Introduction

The default Reception that displays in the Visitor Management application (on the **Home** screen and when creating a new visit), when a Receptionist logs on is determined by the workstation they have logged onto.

This procedure allows you to set a default Reception for a workstation, and an associated door, as well as configure whether or not a physical or on screen (soft) keyboard will be used for Visitor Management Kiosk.

### Operator Privileges

<table><thead><tr><th width="186">Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>"Edit Site" or “View Site”</td><td>view this page.</td></tr><tr><td>“Edit Site”</td><td>edit properties.</td></tr></tbody></table>

### Procedure

1. Click **Configure** from the menu bar.
2. Click **Services & Workstations**.

   The **Services and Workstations** List Window displays.
3. Select the Workstation you want to set the default Reception for.
4. **Right click** and select **Properties**.

   By default the **General** tab displays.
5. Click the **Visitor Management** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-17e10419be34f274c0ba786f8673066e9562f6a0%2Fworkstation_visitormgmttab.png?alt=media)
6. From the **Default Reception** drop-down list, select the Reception that this workstation is located at.

   **Note:** This field is disabled if the operator does not have the privilege to edit the workstation.
7. The **Door** field allows you to assign the door that the Visitor Management application will monitor for card events. However, this cannot be done until you have created the door. Therefore, this step is covered later in [Creating Doors](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/creating-doors.md).

   **Notes:**

   * The door (reader) that you select enables the host to sign in at the kiosk, and the same door can be used to assign visitor cards.
   * Remote (multi-server) Doors can be selected.
   * It is recommended that you turn the readers sound off.
8. If the Kiosk is in an area that needs to be recorded for Evacuation Report purposes, then the reader must be configured as either the entry or exit reader (normally the former) on the Door assigned here.

   It is recommended that the site set up an Access Zone on the Kiosk Door, then give the Kiosk Host Access Groups access to that door, (i.e. put the Access Zone and Schedule on the actual Host Access Groups).

   We recommend sites do the following:

   1. Configure the Kiosk reader on the **Entry Zone** tab of the Kiosk's Door.
   2. Configure an Access Zone on the **Entry Zone** tab of the virtual Kiosk Door.
   3. Add the Access Zone to the Kiosk Admin and Host Type Access Groups (for the Kiosk Visitor Types), so that everyone in that Group will be granted access to the zone, and therefore will be able to sign in.
9. The Visitor Management Kiosk feature is touch screen capable and supports the use of a physical or on screen (soft) keyboard.

   If an external keyboard is going to be used for the Kiosk, check the **Disable Virtual Keyboard** checkbox to disable the soft (virtual) keyboard for the kiosk workstation.

   **Note:** It is recommended that if the kiosk is to have a physical keyboard, the virtual keyboard should be disabled.
10. The **Mail User Agent** section provides the ability to use the VM Operators client email to send an invitation to a Visitor during the Hosts Visit creation and edit process.

    Click the appropriate radio button if required.
11. Click the **OK** button.


---

# 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/setting-default-receptions-for-workstations.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.
