Back to knowledgebase

KASAccess Inner Range Integriti Integration. White Paper

Integration Between KASAccess and Inner Range (Integriti)   1. Executive Summary This white paper describes the integration between KASAccess, the cloud-based access control platform developed by KAS – Keyless Access Security, and Inner Range’s Integriti The integration is intended to enable control of Inner Range Access Control Readers (ACRs) via the Integriti System through the […]

Popular searches

Browse by area

Browse by product

Popular intents

Integration Between KASAccess and Inner Range (Integriti)

 

1. Executive Summary

This white paper describes the integration between KASAccess, the cloud-based access control platform developed by KAS – Keyless Access Security, and Inner Range’s Integriti

The integration is intended to enable control of Inner Range Access Control Readers (ACRs) via the Integriti System through the KAS Access Cloud-based platform.

The integration will reduce manual administration, improve data consistency, and provide users with a more streamlined UI for managing physical entry permissions.

The integration will support the following primary functions:

  • Creating PINs (on supported Inner Range ACRs)
  • Creating RFID Cards
  • Remotely Unlocking Inner Range doors / ACRs
  • Turning Free Passage On / Off on Inner Range doors / ACRs

This document outlines the business requirements, technical architecture, data flows, security requirements, responsibilities, limitations, testing process, and implementation approach.


2. About KASAccess

KASAccess is a cloud-based electronic lock and entry management platform developed and supported by KAS – Keyless Access Security.

The platform manages electronic locks, access control readers, gateways, credentials, users, schedules, lock groups, audit records, and related entry control functions.

Depending on the installed hardware and configuration, KASAccess may support:

  • PIN credentials
  • RFID cards and fobs
  • Mobile credentials
  • Remote lock operation
  • Scheduled entry permissions
  • Automatic credential expiry
  • Lock groups and common areas
  • Door event reporting
  • Battery and device status monitoring
  • Property management system integrations
  • API-based third-party integrations

Further information is available at www.kas.com.au.


3. Purpose of the Integration

The purpose of this integration is to connect KASAccess with Integriti so that associated door hardware can be remotely managed via the KASAccess platform and seamlessly integrate with KAS door hardware (e.g. NEO battery-operated locks).

The integration is expected to:

  • Streamline the UI experience of day-to-day operations
  • Allow a single point of interaction between both systems

4. Scope

4.1 Included in Scope

The initial integration will include:

  • Create PINs and RFIDs in KASAccess
  • Edit existing PINs and RFIDs which were created via KASAccess
  • Synchronize rooms / doors into KASAccess
  • Support remote unlock requests

4.2 Excluded from Scope

The following items are excluded unless separately agreed:

  • Inner Range Door Activity (*Subject to a separate module purchase from Inner Range and additional integration work)
  • Network installation or remediation
  • Inner Range hardware configuration
  • Historical data migration
  • Custom reporting outside the agreed interface
  • Changes to unrelated KASAccess functions
  • Changes to third-party systems outside the integration
  • Support for undocumented third-party endpoints
  • Functions not expressly listed in Section 5.1

4.3 Future Scope

Potential future development may include:

  • Event Logs from Integriti
  • Integriti User Management
  • Integriti Free Passage / Scheduled Timed Zones

Future functions will require separate technical review, pricing, testing, and written approval and may be subject to purchase of additional modules from Inner Range.


5. Business Use Cases

5.1 Use Case: Online Booking

Trigger:
Online Booking via third-party PMS (e.g. RMS)

Process:

  1. PMS sends the relevant record to KASAccess.
  2. KASAccess validates the request.
  3. KASAccess identifies the relevant property, room, lock, or lock group.
  4. KASAccess creates the required credentials.
  5. The credential is queued for delivery to the relevant lock or device.
  6. The credential arrives and is activated on relevant Inner Range & KAS Hardware.

5.2 Use Case: Manual Credential Creation

Trigger:
Reception / Other User wishes to create a PIN/RFID Credential

Process:

  1. User logs into the KASAccess Platform
  2. User opens the key-creation menu in KASAccess
  3. User fills in the relevant information (PIN/RFID number, username, start/end dates)
  4. KAS Sends the relevant credentials to both Inner Range & KAS Hardware.

5.3 Use Case: Credential Deletion

Trigger:
User wishes to revoke a PIN / RFID card

Process:

  1. User logs into the KASAccess system
  2. User locates the relevant PIN / RFID in the Keys list
  3. User selects which doors they wish to revoke access from
  4. KASAccess revokes access from the relevant doors

6. Integration Setup

Process:

  1. User contacts Inner Range for purchase of any modules that will facilitate remote connections
  2. User contacts KAS and either
    1. Provides relevant information for connection (IP Address, Port, Username / Password)
    1. Provides KAS with Remote Access to the host machine to perform remote-access configuration
    1. Self-Configures the connection settings in the KASAccess portal
  3. Configuration is tested by creating a credential on the system
  4. User may contact KAS for assistance if an issue arises during configuration

Assumptions:

  • The hosting machine is reachable and has a static IP address
  • The user has purchased any relevant modules / subscriptions from Inner Range
  • The Integriti Software is fully configured (Site Name, Doors, etc.) to the user’s needs by the Inner Range installer

7. Error Handling

Errors will be classified as follows:

7.1 Validation Errors

Examples:

  • Missing required field
  • Invalid date format
  • Editing Expired Keys

These errors will require the user to validate the data input and retry.

7.2 Temporary Processing Errors

Examples:

  • Temporary network failure
  • Gateway offline
  • Lock unavailable
  • Third-party API / Server unavailable
  • Database timeout

These errors will require the user to physically check relevant hardware for faults (lock batteries, gateway connectivity, internet connectivity, networking, server status, etc).


8. Offline Behaviour

KAS locks may continue to operate using credentials already stored on the device when Internet connectivity is temporarily unavailable.

During an outage:

  • New remote instructions may be sent but they will not land on the lock(s)
  • Credential changes will error out
  • Event information may be delayed
  • Remote unlock may not be available
  • Previously issued valid credentials will continue to operate until their expiration date
  • Keys will continue to expire at their intended date

Related articles

29 Jun 20261 min read

Lock-S – Remote Functionality with Gateways

Premise This guide will talk you through how to connect your Lock-S locks to a gateway and remote control them via the Lock Keeper app. Note: Remote functionality with Lock-S has been deprecated. While this may still work, we cannot guarantee it. ...