> 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-access-to-salto-outputs.md).

# Configuring access to Salto Outputs

### Introduction

A Salto Output number can be assigned to an Command Centre Access Zone item. When a Cardholder's card is encoded with Salto data by Command Centre, the Salto Output numbers for any Access Zones the Cardholder is required to access are added to the card. When a Cardholder presents their card at a Salto wired reader, (i.e. located within a lift), the Salto Outputs for which the Cardholder has access will be activated, thus enabling the Cardholder to access one or more floors.

**Notes:**

* This feature has been designed to work with a low level elevator interface managed by the Salto system.
* This feature supports a Command Centre multi-server environment. However, it is important to note, that the Salto Output number configured for an Command Centre Access Zone item, must correspond to a Salto Output on the *connected* Salto Server.
* Salto Output numbers available are 1-128.
* Multiple Access Zones can share the same Salto Output number.
* The Salto Output number must correspond to a Salto Output in the Salto application, (i.e. a Salto relay on a Salto relay expansion board).
* When using two Salto relay expansion boards, the Output on each relay board will activate at the same time, unless you change the Dip Switch settings on the second board.
* The standard functionality for a Command Centre Access Zone item, (e.g. Lockdown, Cardholder Access Schedule, etc.) does not apply to Salto Outputs. Instead, the Salto Door connected to the control unit, (e.g. CU5000) and relay expansion board can be used to prevent access to the Salto Outputs when in lockdown mode.
* Outputs must be configured in Salto when using Salto encoded guest cards. When using Command Centre encoded cards (encoded with Salto data) the Outputs need only be assigned in Command Centre.

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** on the appropriate Access Zone, and select **Properties**.

   By default the **General** tab displays.
3. Click the **Salto Options** tab.

   **Note:** This tab is only available if your site is licensed for one or more Salto Doors.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-49a87929c97578aae6aab211e4c04a2192df1a5b%2Fsalto_outputs.png?alt=media)
4. Check the **Assign Output Number** checkbox.

   The Output Number field is enabled.
5. Enter the Salto Output number for this Access Zone. Cardholders with access to this Access Zone will have access to the Salto Output.
6. 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 Output has been assigned to an Access Zone 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-access-to-salto-outputs.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.
