> 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/editing-the-salto-server.md).

# Editing the Salto Server

### Introduction

Operators require the "Edit Site" privilege in a division to be able to modify the Salto Server item.

### Procedure

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

   The **Salto** List Window opens.
2. **Right click** on the Salto Server and select **Properties**.

   By default the **General** tab displays.
3. Click the **Settings** tab.

   How the screen looks depends on whether this is a new or an existing site.

   <table><thead><tr><th width="126">If...</th><th>then...</th></tr></thead><tbody><tr><td>a new site,</td><td><p><strong>Encrypted (HTTPS)</strong> is the default "Transport" connection.</p><p>If your site chooses to use Salto Native Mode, settings from the Salto server side need to be changed. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection.md">Salto Server Connection</a> for the procedure.</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-88d44379fc563729eb6d7d308da9ff5f3df48c2a%2Fsaltoserver_settingstab_newsite.png?alt=media" alt="" data-size="original"></p></td></tr><tr><td>an existing site,</td><td><p>there are two "Transport" options to choose from, i.e. <strong>Legacy (STP)</strong> and <strong>Encrypted (HTTPS)</strong>.</p><p>Select the appropriate "Transport" radio button:</p><ul><li><p><strong>Legacy (STP) Transport with Legacy Mode:</strong></p><p>This option is available for STP (TCP/IP) connection, however it is recommended to use the <strong>Encrypted (HTTPS)</strong> option to secure communication.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5631f859a633df56490deeb9e8c8fead4644ac7f%2Fsaltoserver_settingstab_existingsite1.png?alt=media" alt="" data-size="original"></p><ul><li><p><strong>Encrypted (HTTPS) Transport with Legacy Mode:</strong></p><p>If your site chooses to use Salto Native Mode, this option must first be selected. Before changing connections to HTTPS, settings from the Salto server side need to be changed. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection.md">Salto Server Connection</a> for the procedure.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8391568e82a3a7a902cc6466ecf8e5822a0d0877%2Fsaltoserver_settingstab_existingsite2.png?alt=media" alt="" data-size="original"></p><ul><li><p><strong>Encrypted (HTTPS) Transport with Native Mode:</strong></p><p>After the site enabled Native Mode, the Server Connection page will still display the incoming port so that existing Legacy Mode cards can use the STP connection. Completing Native Mode card migration will allow this port to be closed.</p></li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1bcba50b60504d67669d430a97d79f2ff042dde2%2Fsaltoserver_settingstab_existingsite3.png?alt=media" alt="" data-size="original"></p></td></tr></tbody></table>
4. The single Salto Server Command Centre item has the following properties which are valid for the Server only:
   * **Address** of Salto Server (default = empty). This needs to be changed to the Server name or IP Address for the Server running the Salto application, if the Salto Server does not reside on the same PC as the Command Centre Server. It can take up to approximately ten seconds for the Salto server to come online after configuring or re-configuring the Name / IP-Address.
   * **Port** is the port for outgoing requests to Salto Server (Default to 8100 for Encrypted HTTPS and 8095 for Legacy STP).
   * **Incoming Port** is the port for incoming STP requests from Salto Server (Default to 8096).
5. The **DESFire** **SAM Key** section displays by default. The key is randomly generated or you can enter a key in the field, then click **Apply** to send it to the SALTO Space server.

   The key remains visible in the field until it is applied.

   <figure><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2F3cgDAZtePchWMxi6LZyC%2Fimage.jpeg?alt=media&amp;token=61006fc9-d79c-4d2c-a8c6-097d9cbd340e" alt=""><figcaption></figcaption></figure>

   Once applied, the key is no longer displayed. Instead, the section shows which key Command Centre is using, identified by its key ID and creation date (for example, *ID 1: Created 28/08/2026 14:48:15 - Currently using*).

   <figure><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2FF69LAJNgKvpLY7OE8wlN%2Fimage.jpeg?alt=media&amp;token=11a8ddba-110f-4b2d-9bba-4f7aad368d07" alt=""><figcaption></figcaption></figure>

   If you need a copy of the key after it has been applied, you can export it in password-encrypted form from **Server Properties** > **Card Security** > **MIFARE Site Keys** > **Export** **Keys**.\
   **Notes:**

   * You must have the **Manage Keys** privilege to use this feature.
   * The key must be exactly 32 hexadecimal characters (0–9 and A–F), which is a 128-bit key.
   * The DESFire SAM Key can only be set up on new sites.
6. Click the **Cardholder Options** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5076337248855da0be80409eb00da876ee701644%2Fsaltoserver_cardholderoptionstab.png?alt=media)
7. Set the **Card Expiration Period** settings as appropriate:
   * **Normal card access** is the period of time a card can be used until such time as an update at a Salto wired lock is required. (Default is 7 days).
   * **24/7 card access** is the period of time a card can be used, ignoring all Schedules and Day Categories, (e.g. Public Holidays) until such time as an update at a Salto wired lock is required (Default is 30 days).
8. The single Salto Server Command Centre item also has the following properties to set default values for items which are configured by Cardholder:
   * **Office Privilege** defaults to “Off”.

     The Office Privilege enables a Cardholder to override a Salto lock to "Office" (Command Centre Equivalent = Override to Free) mode, when the lock is scheduled to allow this override (Office mode).
   * **Privacy Override Privilege** defaults to “On”.

     The Privacy Override Privilege relates to locks that come fitted with an internal privacy button, disallowing Cardholders from entering while this button is pressed. Those with the Privacy Override Privilege will be able to enter through locks that have this button activated.
   * **Low Battery Warning** defaults to “Off”.

     This setting defines whether or not Low Battery events are written to cardholders' cards, as default. Cards must be formatted with 6 or more sectors in order for this event to be passed to the cards.
   * **Mobile Events** defaults to "On".

     When checked, if a cardholder gains access via the Mobile App, even if the Salto door is offline, events will go through to the Cloud and then to Command Centre.

     **Note:** This feature will have a small delay in activating upon upgrading from a previous Command Centre version. The settings will go out with the next Salto key update, which is typically the next day. Users that are offline will not get the update though, and it may take up to 7 days for all users to get the key update as the expiry for the key is 7 days.
   * **24/7 Accommodation mode**

     There are two operating modes available - **"Normal"** and **"24/7 Accommodation"** modes. The system default is Normal mode, (i.e. the 24/7 Accommodation mode checkbox is **not** checked.

     In both modes there is a default number of days that cards must be able to work at Salto wireless readers before the card must be badged at a Salto wired reader in order to maintain their access rights for Salto doors. This period is measured from the start of the day the card was last updated at a Salto wired reader.

     Default for Normal mode is 7 days between wired updates but can be configured to be less or more than this (valid range is 1 hour to 999 days).

     "24/7 Accommodation" mode ignores all schedules in Command Centre and therefore allows longer periods than 7 days to be specified before cards have to visit a wired reader. Default for this mode is 30 days (same as default expiry in Salto application) but can be configured to be up to 365 days (valid range is 1 hour to 365 days).
   * **Activate ESD Relay 1 and 2** default to "On".

     A Salto Door Command Centre item may correspond to a Salto ESD (Energy Saving Device).
   * **Automatic Key Assignment**

     When checked, the Automatic Key Assignment feature is enabled from Salto for a cardholder. Refer to [Salto Key Assignment](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/salto-key-assignment.md) for further detail.
9. Click the **Calendar Options** tab.

   This tab applies to Salto Native Mode only. Therefore, if your site is using Legacy Mode, refer to [Changing SALTO Server to Encrypt HTTPS connection in Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-installation-instructions/6-salto-server-connection/2-changing-to-https-connection-in-command-centre.md) for the procedure.
10. 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

The settings of the Salto Server have been modified and will take effect after saving the changes.


---

# 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/editing-the-salto-server.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.
