> 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/opening-the-salto-list-window.md).

# Opening the Salto List Window

### Introduction

The Salto-specific List Window displays the Salto Server and any Salto Doors, ESDs (Energy Saving Devices), Lockers, Rooms, Suites and Access Zones that have been created within the Salto application. The Salto Server is the single parent item and all Salto Doors, ESDs, Lockers, Rooms, Suites and Zones appear as children of that parent.

### Procedure

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

### Result

The Salto List Window displays.

To refresh the Salto List Window, **right click** on the Salto Server and select **Update Access Points**.

The Salto List Window will be updated to display any Salto Doors, ESDs, Lockers, Rooms, Suites and Access Zones.

Immediately upon connecting to Salto server the Salto List Window lists Doors under their assigned Zone if they belong to only one Zone.

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

The "Salto Server" item is automatically created when the Command Centre Service starts, if it does not already exist, and the license file contains a count of Salto Doors that is greater than zero, (i.e. Salto Doors=nnn in the \[Limits] section of the license file). It is initially named "Salto Server", and is placed in the Root Division, though the division can be changed later. There can only be one of this item, and it cannot be deleted.

**Note:** The "Salto Server" item can be placed in the Status Viewer, used on Site Plans, and in Site Configuration Reports.


---

# 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/opening-the-salto-list-window.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.
