InnerWeb
Skip to main content

Access Control Integration with InnerWeb: Recommendations for IT and Security

The plant has a working access control system and does not intend to replace its readers, but wants card swipes to connect with qualifications, work permits and time recording. Below are six recommendations for IT and security: from defining the scope, through the specification for the supplier, to testing and maintenance.

2
versions of the platform REST API (v1 and v2, JWT)
Source: karta

Assumption: we do not replace the readers

InnerWeb is a software producer, not a device maker. It does not manufacture or replace access control readers or access control cards. It integrates with the client's existing access control system, which continues to open doors and gates. This principle simplifies the project: the scope of work concerns the interface between the systems, not the infrastructure in the field.

InnerWeb is an independent system that complements the client's existing systems: access control, time recording, HR and ERP. It is not a replacement for them, so contracts and warranties for the current systems remain unchanged.

Six recommendations

The order follows the course of the project.

1. Start with the question of which decisions depend on a swipe

A card swipe is a raw event. Define what it is for: the verdict at the gate, presence on site, time recording, contractor settlements, or all of them at once. The scope decides which fields the event should contain and how quickly it needs to arrive.

2. Hand the event specification to the access control supplier

In a real pattern at a packaging manufacturer, the integration of swipes from the access control system to time recording was built according to a specification handed to the access control supplier, without InnerWeb readers. The specification describes the event format, card identifier, control point, timestamp and direction of passage.

3. Choose the webhook as the primary channel

InnerWeb receives card swipe events from the access control system by webhook. The platform also provides a REST API in versions 1 and 2 with JWT authorisation, so data can be supplemented and bidirectional integrations are possible if the access control supplier supports them.

4. Agree the identity of the event with the person's account

On installations with entry cards, the training result is carried over to the account with the card, and the system never merges accounts by surname alone. Before go-live, check that every card in the access control system has an account in the complementary system and that the identifiers match.

5. Test the edge scenarios

Test cards with a missing training, blocked cards, group entry, loss of connectivity and resending of events. When a valid occupational safety training is missing, the system creates an alarm permit and notifies the company coordinator, so this scenario is worth checking first.

6. Plan maintenance and monitoring

An integration without monitoring goes silent. Define who checks delays, who reacts when a given gate stops sending events, and who is responsible on the access control supplier's side. Record these roles before the system goes live.

Example integration project duration by stage (working days)

Example integration project duration by stage (working days)Bar chart with the duration of integration stages: 5, 13, 8 and 3 working days051015daysSpecification: 5 days5 daysSpecificationSupplier work: 13 days13 daysSupplier workTesting: 8 days8 daysTestingGo-live: 3 days3 daysGo-live
Source: Example calculation: illustrative assumptions for one plant, not values from a specific rollout

Split of roles between IT, security and the supplier

IT is responsible for the network, authentication and the security of the interface. Security defines the control points and the gate scenarios. The access control supplier prepares event dispatch according to the specification and maintains the controllers. InnerWeb is responsible for receiving the events, linking them with permissions and presenting the verdict.

It is worth recording these roles in one document with contact numbers for emergencies, because the most common cause of an integration break is the lack of an owner on one of the sides.

  • IT: network, authentication, connectivity monitoring.
  • Security: control points and gate scenarios.
  • Access control supplier: event dispatch and controllers.
  • InnerWeb: receiving events, permissions, verdict.

What to avoid

Do not promise management a replacement of the access control system as part of the integration. Do not assume either that an encrypted card will solve the permissions question on its own: it verifies the identity of the credential, and entry is decided by the permissions on the system side. Do not skip tests on the production network. If the OT policy blocks outgoing traffic, plan a queue and a poller, which we describe in the material on the webhook from the access control system.

Video

Frequently asked questions

Does the integration require replacing the readers?

Not from the InnerWeb perspective. InnerWeb does not manufacture readers and does not replace them: it integrates with the client's existing access control system.

Who prepares the event dispatch?

The access control supplier, according to a specification agreed with the plant. This pattern was used for the integration of access control swipes with time recording at a packaging manufacturer.

Does InnerWeb replace time recording?

No. InnerWeb complements access control, time recording, HR and ERP by linking swipe events with qualifications, work permits and presence.

Sources

Plan the integration with us

We will help prepare the event specification for your access control supplier and agree the scope with IT and security. Book a conversation.

Let's talk