> 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/space-installation-instructions/6-salto-server-connection/1-changing-settings-in-salto-space.md).

# 1. Changing settings in SALTO Space

Before changing connections to HTTPS in Command Centre Configuration Client, settings from the Salto server side need to be changed, as follows:

1. Log on to Salto Space.
2. Select **System** > **General options** > **SHIP**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-556d9873285ebcc7bd2499d861eabd51e6728238%2Fsaltospace_shiptab.png?alt=media)
3. Change Transport Protocol to **HTTP(S)**, and select "Custom" from the **Authentication** drop-down list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-03d7cd4e15a81e38d7a148caeab9829310c75ed8%2Fsaltospace_httpsoption.png?alt=media)
4. Create a unique key in the **Key** field, then re-type it in the **Confirmation** field and click **Save**.

   **Notes:**

   * This key is based on a custom token that a client provides when making HTTP requests. API keys are supposed to be a secret that only the client and server know.
   * Once the key is populated, it won’t be able to see anymore from Salto Space.
5. Double-click the **ProAccess SPACE Configurator** icon on your desktop.
6. From the **Service Properties** tab, click the **STOP** button to stop the Salto services.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-afcc35e88cfa8e8d51c0dc9fc5d7398bf60e417c%2Fsaltospace_serviceproperties.png?alt=media)
7. Select the **Service ports** tab and tick "Use HTTPS"checkbox.
8. Choose the correct certificate from the drop-down list.

   **Note:** Please consult your IS department for the certificate to be installed.

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

   **Notes:**

   * If you skip Steps 5 - 7, when Command Centre changes to HTTPS connection, the following warning message will display:

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e9bf886341ea424f7b0384593b0ab92ef1ba3a03%2Fsalto_warningmessage.png?alt=media)
   * If the certificate has changed from the Salto side, the Command Centre will lose connection with the Salto Server.
9. Click the **Start** button to start the Salto services.
10. Click **VERIFY** for Salto authentication Port to check your port is working, and then click **SAVE**.
11. Return to Salto Space and select **System** > **General options** > **Users**.
12. Within the 'Settings' section, select the **Discarded openings are also included in the key's auditor** check box.

    This setting is required for unauthorised events with offline doors to be raised in Command Centre.
13. Within the 'Tracks of user key section', Gallagher recommends ensuring the **Wiegand code** checkbox is selected and **Profile code** is selected.

    This is required for when you create third party doors using UBOX4000 or other wired door controllers.
14. Click **Save**. If a Warning window displays, click **Yes**.


---

# 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/space-installation-instructions/6-salto-server-connection/1-changing-settings-in-salto-space.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.
