> 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-doors.md).

# Creating Doors

### Introduction

A Door needs to be configured in Command Centre if your site intends using reception readers.

**Notes:**

* If access cards are to be assigned to visitors or will be used for identifying and assigning escorts, a Door will need to be configured for each Reception workstation requiring such functionality.
* If visitor access cards are to be used, and visitors will be leaving the site through a different reception from the one they arrived at, a Door needs to be configured for the exit reader.
* Doors should be created in the "Visitor Division" as the Receptionist will need the "Events and Alarms" privilege to see the Door and the result of the card swipe.

### Procedure

1. Click **Configure** from the menu bar, then **Doors**.

   The **Door** List Window opens.
2. **Right click** and select **New\...Door**.
3. Configure the new Door as required.

   See [Creating Doors](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/creating-doors.md) for further detail.
4. Click **Configure** from the menu bar, then **Services & Workstations**.

   The **Services and Workstations** List Window opens.
5. Double-click on the Reception workstation.
6. Click the **Visitor Management** tab.
7. From the **Door** drop-down list, select the applicable Door. Remote (multi-server) Doors can be selected.

   The Visitor Management application will monitor this door for card events.

   **Notes:**

   * Where more than one workstation is configured for a single reception and access cards are used, it is advisable to configure one reader per workstation to prevent unexpected events occurring at another workstation when a card is badged.
   * Ensure escorts (in the Host Type Groups) have access to the door selected.


---

# 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-doors.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.
