> 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/site-installation/elevator-cars/high-level-interface-elevator-cars/copying-an-elevator-car.md).

# Copying an Elevator Car

### Introduction

This procedure enables an operator with the "Edit Site" privileges to create a new elevator car that is a copy of an existing elevator car. Use this procedure when you are creating a new elevator car that provides the same access to floors as an existing elevator car. For example, you could use this procedure when creating an Elevator Car HLI that is part of the same group as an existing Elevator Car HLI.

**Note:**

You can copy either standard elevator cars or high level interface elevator cars using this procedure.

### Procedure

1. Click **Configure** from the menu bar, then **Elevator Cars**.

   The **Elevator Car** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the elevator car you want to copy and select **Duplicate**.
3. A new elevator car is created.

   <table><thead><tr><th width="192">If you copied....</th><th>Refer to....</th></tr></thead><tbody><tr><td>a standard elevator car</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/low-level-interface-elevator-cars/configuring-elevator-cars.md">Configuring Elevator Cars</a>.<br>All elevator car properties are copied except the Reader, Inputs and Outputs, which will be different for each elevator car. Enter the Reader, and the Outputs and Inputs for each floor. Change the Name and amend other properties if necessary.</td></tr><tr><td>an Elevator Car HLI</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars/configuring-an-elevator-car-hli.md">Configuring an Elevator Car HLI</a>.<br>All elevator car properties are copied except the Reader, which will be different for each elevator car. Enter the Reader and change the Name, Group number and Car number. Amend other properties if necessary.</td></tr></tbody></table>
4. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A new elevator car is created with selected properties copied from an existing elevator car. The Controller that supports the Elevator HLI will begin polling the elevator system.


---

# 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/site-installation/elevator-cars/high-level-interface-elevator-cars/copying-an-elevator-car.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.
