<aside> Date Created: November 28, 2022 Last Updated: November 3, 2025

</aside>

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" /> This document describes the Floorsense database format and methods for automating the importing and updating of user data including swipe card numbers, email address and optional attributes such as fixed desk reservations.

</aside>

Smartalock-Floorsense User Database Import and Export v4.2 Dec 2020.pdf

Contents:

Smartalock / Floorsense User Database Import / Export – IntegrationGuide

1.0 Overview:

The Smartalock/Floorsense system maintains a database of users, RFID cards and reservations on the master controller. This document describes

• The basic topology for connecting over IP network to Smartalock/Floorsense Master controller (sometimes called Primary Controller)
• A description of the database as stored on the Master controller
• How to go about importing users, their swipe cards and other useful data such as email addresses or unique IDs into the system from an external system (such as a building access card database)
• The methods to keep the Smartalock data updated
• How to export the database from Smartalock master server for backup or quick editing and re-importing. This maybe faster than using the Web interface.

Generally integration with the Master controller occurs over its “outside” LAN interface which connects into the customers network via a DMZ. Over this network both the web administration of the system can be performed, and also the automated or manual uploads of the customers end-user names, current access card numbers, and optionally other user data such as email addresses, locker and desk fixed reservations from an external source system

Internally the Master Controller maintains the complete user database including all card numbers and locker/desk reservations for the entire site. Sections of the entire database will be transferred and deleted from slave controllers (at individual locker banks or other locations) as required - such as when a user creates or releases a reservation on a particular locker bank or desk, then the relevant parts of the database are downloaded automatically to the slave controller.