> 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-site-configuration/salto-user-and-ship-settings.md).

# Salto User and SHIP settings

### Introduction

You must configure the SALTO Host Interface Protocol (SHIP) option by using the SHIP tab. When SHIP integration is performed, only doors are managed by the SALTO system. Users are managed in Gallagher Command Centre, and synced with Salto Space.

### Procedure

1. Select **System > General options > Users**.

   The Users tab displays.
2. Within the 'Settings' section, select the **Discarded openings are also included in the key's auditor** checkbox.

   This setting is required for unauthorised events with offline doors to be raised in Command Centre.
3. 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.
4. Select **System > General options > SHIP**.

   The SHIP tab displays.
5. Enable the SALTO SHIP SERVER to communicate with Gallagher Command Centre.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-360691c2f85b5ca06f801b5f27019c5f38c79cb3%2Fsaltoshipportsettings_1.png?alt=media)
6. Configure as appropriate.

   <table><thead><tr><th width="220">Checkbox/Field</th><th>Description</th></tr></thead><tbody><tr><td>Enabled <em>for SALTO SHIP SERVER</em></td><td>Enables the SALTO SHIP server.</td></tr><tr><td>Limit communications to one server</td><td>Limits communications to one server in the network. When you select this option, you must enter the IP address for the third-party server you have selected for the communications in the <strong>IP address</strong> field underneath the checkbox. This means that the SALTO software will only communicate with that server (using SHIP protocol). If you do not select this option, other servers in the network will be able to send commands to the SALTO server.</td></tr><tr><td>Transport Protocol</td><td><p>Native mode uses <strong>HTTP(S)</strong>. Select "Custom" from the <strong>Authentication</strong> drop-down list.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ac7105385a931d452abf00097e65baf7834d7bbd%2Fspace_transportprotocol.png?alt=media" alt=""><br>Create a unique key in the <strong>Key</strong> field, then re-type it in the <strong>Confirmation</strong> field.</p><p><strong>Notes:</strong></p><ul><li>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.</li><li>Once the key is populated, it won’t be able to be seen anymore from Salto Space.</li></ul></td></tr></tbody></table>


---

# 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-site-configuration/salto-user-and-ship-settings.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.
