How to onboard Salto Space
How to onboard Salto Space with Unloc
Version
This is version 7 of this document for Salto Unloc Proxy v1.0.3. This link will always point to the latest available documentation online.
What is it?
Salto Space is an on-prem solution running on a Windows machine. Unloc has implemented a system, the SALTO Unloc Proxy, that communicates with the on-prem machine in order to create, revoke and refresh keys. The Unloc Salto Proxy runs as a service alongside the other SALTO services on the server.

Screenshot from the Windows Management Console.
Requirements
- A Salto Space installation can use Unloc, given the following requirements.
- The site server must be running Salto Pro Access SPACE version 6.9.1.0. or later.
- The site server is permanently turned on.
- The site server has an internet connection.
- The site owners must purchase a SHIP license from Salto. The SHIP license is an extension to the Salto Pro Access SPACE software.
- The site server must run Windows 10 or newer
- Encoder must be ethernet-type (not USB)
- Locks must be BLE-enabled
Files
- Installer.exe
- config.json
- credentials.json
Installation
- You should have received the files as a password protected zip file. Make sure to unzip the content using the password you received from Unloc.
- Run the provided installer.exe executable on the same machine running Salto SPACE. The installer will copy necessary files to c:\program files\unloc. You may need to run the installer.exe as an administrator.
NOTE: Later versions of Windows may attempt to block the opening of installer.exe with a warning. If this happens, then click “More info” and “Run anyway”. See the below screenshot (in Norwegian).

- Copy the two provided files: “config.json” and “credentials.json” to the installation directory c:\program files\unloc. These are configuration files specific for this installation and allow the installation to communicate with the Unloc platform. Note: These files should be considered confidential, so please do not copy or share these files with anybody else.
- Open c:\program files\unloc and launch c:\program files\unloc\setup.bat. This will install and start the SALTO Unloc Proxy as a Windows service.
Salto Pro Access SPACE configuration
In order for Unloc to be able to interact with Salto Pro Access SPACE, the following configurations need to be made.
Connection configuration
Under System/General Options/SHIP: enable SALTO SERVER (SHIP) on port 8888.

Lock configuration

Navigate to system → General Options → Access points, then under "General Purpose Fields", check "Enable field 1" and put "Unloc" into the text field.

Set lock type
Each lock (under Access Point/Doors) that should be Unloc-compatible needs to set the field "Unloc" to the correct lock type id. The lock type id used should correspond to the actual lock that is installed.
For example, if an Access Point named “Office One” is a Salto NEO Cylinder, then the lock type id for that lock should be set to “neo”:
The list of available lock type id’s is listed below. Use “generic” if you’re unsure which lock type to select.

Lock Type IDs |
generic |
neo |
neoxx |
mini |
aelement |
one |
original |
original-keypad |
locker |
wallreader |
wallreader-keypad |
Enable audit on keys
To get correct key events and battery status reported back to the unloc platform you also need to enable “Audit on keys” on all doors that are used within Unloc. This will require you to update the doors with a PPD.

Encoder configuration
In order to generate and encrypt the data needed to open a lock with the Unloc app, you need to set up a network encoder, defined as a dongle.
- Go to System -> Salto Network

- Then add a new network device of type "Encoder". Give it a name, an IP address and then save. Hold the CLR-button on the encoder until the light blinks, then click on "assign IP address".
- Go to System -> Salto Network
- Choose an online encoder you want to dedicate to creation of unloc Keys and check the “Enable dongle mode” checkbox

Next, we need to activate BLE and NFC functions in the locks, so that the Unloc app is able to communicate with the lock.
- Go to System -> SAM & Issuing options
- Under "inactive keys" you will find BLE and HCE. Mark both of these so that they move up into "active keys", then save. Update all doors with PPD.

Denylist configuration
Keys created by Unloc should not occupy slots on the denylist. In order to ensure this, you must follow these steps:
- Go to System -> General Options -> Advanced
- Add a new parameter: MORE_THAN_64K_USERS and set its value to 1
The result should look something like this:

Final step
The last step is to restart Salto ProAccess Space Service (select Services from Windows start menu).
Naming locks on hosted server
If you have a hosted solution with several customers on the same server you need to give the locks a prefix that makes it possible for us to identify all the locks connected to a specific customer. Prefixes can be numbers or letters as long as they are unique per customer (e.g 220 or CBT).
All locks connected to that customer have to start with the same prefix for us to understand who it is connected to, Unloc does not see the information written in “Description” on the Salto site.
Uninstall
From a terminal:
Enter the Unloc installation directory: cd “c:\program files\unloc”
Stop the service: .\nssm stop "SALTO Unloc Proxy"
Remove the service: .\nssm remove "SALTO Unloc Proxy"
Updated on: 23/01/2026
Thank you!