> 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/creating-a-reception.md).

# Creating a Reception

### Introduction

This procedure describes how to create a Reception in Command Centre.

### Operator Privileges

<table><thead><tr><th width="402">Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>“View Site”, "View Visits", "Edit Visits" or "Manage Receptions"</td><td>view a Reception's properties.</td></tr><tr><td>“Edit Site”</td><td>create and/or change a Reception's properties.</td></tr></tbody></table>

### Procedure

1. Click **Configure** from the menu bar.
2. Click **Receptions**.

   The **Receptions** List Window opens, displaying the Receptions that the operator can view or edit.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d4fb48faab2d5bbcb280abcca013343deb378b30%2Freceptionmlw.png?alt=media)
3. **Right click** and select **New…Reception**.

   By default the **General** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f7b1266e6fedff4db44ecb094e66de6fea1368f0%2Freception_generaltab.png?alt=media)
4. Type in a **Name** for the Reception and a logical **Description**.

   **Note:** Use meaningful names for Receptions, as they will appear throughout the Visitor Management application.
5. Assign the Reception to a Division.

   **Notes:**

   * Each Reception can only be assigned to a single division.
   * Divisions are used to configure the way the Visitor Management application operates for each Reception. Receptions that share the same configuration should be held in the same division, (i.e. usually in the **Visitor Division**, however for more complicated setups refer to [Configuration Examples](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/configuration-examples.md) to determine which division the Receptions should be assigned to).
   * Receptions should be saved in the Division with the configuration.
6. Do you want to configure a default visitor type for this Reception?

   If **yes**, go to Step 7.

   If **no**, got to Step 9.
7. Click the **Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-18b2ad0eedbea3a8e243dd0a0ef1e9eba8d9bbde%2Freception_defaultstab.png?alt=media)
8. Select a **Default Visitor Type** from the drop-down list for this Reception.

   The visitor type selected will be used by default when creating a new visit in Visitor Management.
9. Click the **OK** button to exit and save your changes.

### Deleting Receptions

A Reception can not be deleted if it is the:

* default reception for a Workstation (see [Setting default Receptions for Workstations](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/command-centre-site-configuration/setting-default-receptions-for-workstations.md)), or
* reception for a visit.


---

# 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/creating-a-reception.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.
