> 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/integrated-systems/salto-lock-interface/command-centre-site-configuration/configuring-salto-doors.md).

# Configuring Salto Doors

### Introduction

Salto Doors, Salto Lockers, Salto Rooms, and Salto Suites are treated as Salto Door items in Command Centre.

Salto Door properties are editable in Command Centre with the "Edit Salto Items" operator privilege, once the Salto Door, Salto Locker, Salto Room, or Salto Suite has been transferred from the Salto Server, (i.e. Salto Doors are automatically created in Command Centre once an ‘Update Access Points’ operation on the Salto Server has occurred).

Changes made to Salto Door names and descriptions in Command Centre update automatically in Salto without performing an ‘Update Access Points’, when Salto is online, or comes online after being offline. Likewise, Salto Doors can be deleted from Command Centre and the deletion occurs automatically in Salto when Salto is online.

### Procedure

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

   The **Salto** List Window opens.

   **Right click** on the appropriate Salto Door, and select **Properties**.

   By default the **General** tab displays.

   **Notes:**

   * If you change the name in Command Centre, you need to right-click on Salto Server and click 'Update Access Points' and the changes will be updated.
   * The **Division** that appears on the **General** tab will be the last division used by the operator that did an 'Update Access Points' of the Salto Server. Check this is the required division.
2. If using the Salto Space integration, click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a1714624062fc11714430175ee3260965a1acb77%2Fccdoorstatusoverrides.png?alt=media)

   Overrides that can be performed using the Salto Space integration are: Open Door, Emergency Opening and Lockdown.

   **Note:** Salto online doors can be added to a [Macro](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/macros.md) which will enable you to Lockdown multiple Salto online doors simultaneously.
3. Click the **Related Zones** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-70a5ea0f85a3daa7fd0f9d9a78ca9b1f93d68401%2Fccdoor.png?alt=media)

   This screen shows the Salto Access Zone(s) that this Salto Door belongs to. Salto Access Zone(s) can be added to this screen using drag-and-drop, or removed by right-clicking on the Zone and selecting **Delete**.
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 Salto Door has been configured in Command Centre.


---

# 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/integrated-systems/salto-lock-interface/command-centre-site-configuration/configuring-salto-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.
