InVentry & Salto Pro Access Integration Information
Learn how to seamlessly integrate InVentry with your Salto Pro Access System, including essential technical requirements and features for user synchronisation, Mifare token management, and system preparation
System Preparation
There are a number of ways in which InVentry can be integrated with your Salto Pro Access System:
User Synchronisation
The ability to automatically synchronise personnel from the InVentry visitor sign-in system and create them within the access control system removing unnecessary administration time to the end user.
User Association
The ability to synchronise personnel from the InVentry visitor sign in system with users that already exist as part an existing access control database.
Mifare Synchronisation
The ability to register mifare tokens & keys within the InVentry visitor sign in system and automatically synchronise to the access control provider.
Listeners
The ability to record activity at a specified location and record back to the InVentry system (this in turn updates the InVentry fire evacuation list).
Technical Requirements for Integrating InVentry with Salto Pro
To enable your InVentry system to integrate with Salto Pro Access, you will need to meet the following technical pre-requisites:
- InVentry must be running InVentry version V4 upwards.
- InVentry and Salto Pro Access database must be on the same network with two-way communication.
- ‘Alarm Events’, ‘DB Synchronization’ and ‘Automatic key assignment’ modules must exist as part of the Salto Pro Access Space license.
- Salto Pro Access version is 6.5.4 or higher.
- An operator within Salto Pro Access called ‘InVentry’ with administrator permissions can be provided.
- The integration between InVentry and Salto Pro Access is achieved by using an on-premise SQL database and creating a ‘staging table’, as such InVentry require the customer to create a new SQL database named ‘Salto Staging Table’ with ‘Admin’ and ‘Public roles’. Instructions for how to install an SQL server & creation of a Salto staging SQL table can be found by clicking HERE.
InVentry / Salto Pro Access Systems Data Processing
Data will be processed as described below depending on how you set up your system, as discussed with your project manager:
- Where there is no direct integration between InVentry/Salto Pro Access systems, no data is transferred between the two systems.
- Where integration is established between the systems where the accounts previously exist independently in both;
- The systems will require only the transfer of user ID’s.
- The purpose of this is to uniquely identify each user and synchronise activity data.
- Where InVentry is used to create new accounts in Salto, the following data is transferred;
- InVentry to Salto – First name, middle name, surname, Key, InVentry system ID
- Salto to InVentry – Salto ID
The purpose of this is to uniquely identify each user and synchronise activity data. Please note that all data is transferred across the local area network.
For Support Purposes
InVentry will provide support as agreed in your contract. The support team will only have access to the data hosted in your InVentry system and will have no further access without specific consent.