Commercial access control
Inner Range Integriti is a security and access-management platform considered for larger, more integrated or multi-site environments. Its breadth makes design discipline more important: roles, partitions, integrations and change control need to be planned before the database grows.
Use enterprise capability for a defined need
Central administration, large user populations, multiple sites, detailed permissions and integrated security operations can justify an enterprise platform. A smaller project may not benefit if the organisation lacks the people and processes to administer it.
Document present requirements and realistic growth separately so capacity is not confused with necessity.
Model permissions and ownership
Define operator roles, site boundaries, approval paths and access groups. Decide which team owns servers, networks, backups, updates, identity data and incident response. Privileged changes should be attributable and reviewed.
A multi-site system also needs a plan for communications loss and local operation at each property.
Specify integrations precisely
Integriti projects may involve intrusion, CCTV, intercom, lifts, gates or third-party software. Confirm the supported interface, version, licence, event mapping and responsibility on both sides.
High-level software integration provides different information and failure modes from a relay or shared credential.
Control commissioning and future change
Test representative users, schedules, door events, alarms, failure states and operator workflows. Retain approved configuration records and use change control when adding sites or integrations.
All product capacities and compatibility statements require confirmation against current Inner Range documentation and the proposed architecture.
Use Integriti when the operating model justifies an enterprise platform
| Requirement | Potential platform value | Design evidence still required |
|---|---|---|
| Multiple controllers or sites | Central administration with local field operation and structured permissions. | Site hierarchy, WAN dependencies, local resilience, naming and support ownership. |
| Security operators | Purpose-specific monitoring, event handling, maps and operator permissions may support a control-room workflow. | Operator roles, alarm priorities, response instructions, evidence and failover. |
| Business-system integrations | Supported integrations can reduce duplicate user administration or connect events with other systems. | Authoritative data source, field mapping, error handling, licences, versions and rollback. |
| Complex access rules | Structured permissions can represent sites, zones, time profiles and qualified user groups. | A maintainable access model tested against starters, movers, leavers and exceptions. |
Inner Range positions Integriti for central management across multiple controllers and sites, with software editions and features varying by requirement. Confirm the proposed edition and modules using the current Inner Range enterprise solution overview and exact product documentation.
Worked example: three sites with central security and local continuity
A business has a head office, warehouse and production site. Human resources is the source for employee status; local managers approve restricted zones; a security desk investigates forced doors and alarms; each site must keep making authorised door decisions during a WAN outage. This is a platform and governance problem, not merely a door count.
An Integriti design could be shortlisted if the supported configuration can separate HR data import from access approval, apply consistent user identities, preserve local controller operation and present actionable events to authorised operators. Acceptance testing should simulate a new starter, role transfer, immediate leaver, integration failure, WAN outage and recovery. Do not promise an integration until its current interface, licence and responsibility boundaries are confirmed.
Integriti architecture review
| Area | Decision |
|---|---|
| Scale | Current and realistic doors, sites, users and events? |
| Operators | Roles, partitions, approval and audit? |
| Infrastructure | Servers, databases, network, backup and recovery? |
| Integration | Supported interface, version, licence and owner on both sides? |
| Site resilience | Local behaviour during central communications loss? |
| Change control | How are additions, updates and configuration changes approved? |
Design the exception workflow
For Inner Range Integriti, normal authorised use is only one test. Document the lost credential, unavailable administrator, communications outage, power issue, user who cannot use the preferred method and opening that does not return to its secure state. Name who responds and what they may safely do.
Acceptance evidence
- Current models, firmware, software and licences
- Approved door, user and permission schedule
- Normal, denied and exception test results
- Power, network and service-failure behaviour
- Integration cause-and-effect results
- Administrator roles, backups and update ownership
- Known limitations and outstanding actions
Frequently asked questions
How should the door scope be set for Inner Range Integriti?
For Inner Range Integriti, control doors where managed entry creates a clear operational or security benefit. Survey all related entry, exit and emergency routes before deciding.
Can existing credentials be retained for Inner Range Integriti?
For Inner Range Integriti, possibly, but credential technology, encoding, ownership and security should be verified before promising reuse.
Who should administer Inner Range Integriti?
For Inner Range Integriti, nominate trained people with enough authority to approve, change and remove access. Limit privileged accounts and review them regularly.
Which integrations are useful for Inner Range Integriti?
For Inner Range Integriti, often, but the precise interface, licence, event flow and failure behaviour must be confirmed for the proposed products.
What information supports a quote for Inner Range Integriti?
For Inner Range Integriti, provide door photos or plans, user numbers, operating hours, credential preferences, integrations, site constraints and expected growth.
Prepare an access-control brief
Send Serious Security the door locations, approximate user numbers, plans or photographs, required integrations and likely growth. The team can assess the site and prepare an itemised proposal for Sydney or Melbourne.
Request an itemised access-control quote Sydney: (02) 8734 3250 Melbourne: (03) 8513 0799
