InnerWeb
Skip to main content

Card block in the access control system and the account in the OHS system

When a card block in the access control system does not reach the OHS system, the employee is blocked at one gate while still identified at another. We give implementation notes for the integrator and the IT department: what to agree before go-live so that both systems say the same thing.

404
same response for an unknown and a revoked code
Source: product specification
3
minimum number of characters in the card-holder account search
Source: product specification

Division of responsibility between the systems

The first note concerns the boundary of responsibility. InnerWeb is a software producer and does not make or replace access control readers. It receives card punch events from the client's KD system through a webhook and links them with qualifications, permits, attendance and time recording. Active cards, readers and label printers are bought and integrated, not manufactured.

The consequence: the procedure for physically blocking a card belongs to the KD system, while the procedure for access and attendance belongs to InnerWeb. The integrator must therefore agree with the IT department which events the KD system passes on and in which direction the information about a block travels.

Note 1: the direction of the block information

A punch event flows from the KD system to InnerWeb. Information about a card block must reach the attendance system by the same or a parallel route, or be entered by a role named in the procedure in both places. Without agreement a gap arises: a card blocked in the KD system is still linked with the account in the OHS system.

The effect on the InnerWeb side is clear: at the gate a revoked RFID card stops identifying its former owner, because the card lookup skips cards with a revocation date. It is only necessary to ensure that the revocation date appears on the day of the block, not in the next synchronisation cycle.

Parameters of the card-holder account search

Parameters of the card-holder account searchThe search requires at least 3 characters and returns up to 13 results.051015valueMaximum number of resultsMaximum number of results: 13 value13Minimum number of charactersMinimum number of characters: 3 value3
Source: Security panel function documentation

Note 2: duplicate accounts and the training path

When cards are migrated or the system is changed, two active accounts of the same person often appear. The system then transfers the training result to the account with the card, but never merges accounts based on the surname alone. The integrator should prepare a list of duplicates for manual resolution before go-live.

A known difference worth describing in the implementation documentation: in the path of the training tablet, which checks the training status by card, the card lookup does not filter out revocations. This distinction is deliberate, because no decision on physical access is made there. For security, the gate decides, not the tablet.

Note 3: scanner, keyboard and symbology

Some plants use scanners at the gate next to card readers. An incorrect keyboard country setting in the scanner can turn a valid QR code into an unknown one, so the system makes a second matching attempt with a reversed keyboard layout. This safeguard does not replace correct configuration.

Changing the scanner interface, for example from a USB keyboard to a serial port, resets the symbology settings to their defaults, so after each such change the reading of a QR code with an address must be checked.

Test on go-live day

Before go-live, run a trial on a test account: block a card in the KD system, check the status in the attendance system, make a scan at the gate and check that the refusal has the correct reason. Note that an unknown code and a revoked code both return the same 404 error at the gate, so the test cannot rely on telling the messages apart, only on the ledger and the register.

  • block the test card in the KD system,
  • confirm the revocation date in the attendance system,
  • scan the blocked card and check the refusal entry,
  • check the list of duplicate accounts,
  • check the reading of the QR code after a change of scanner interface.

Checklist

Video

Frequently asked questions

Does InnerWeb block the card in the KD system itself?

No. The physical block is carried out by the client's KD system, while InnerWeb receives punch events and manages access and attendance.

Why does the training tablet show the status of a revoked card?

This is deliberate, because no decision on physical access is made in that path. The gate makes the decision.

Does the account search show the card number?

No. The card-holder account search does not reveal the card number.

Let's agree the integration with your KD system

We will prepare a specification of events for your KD system integrator and a list of tests for go-live day.

Let's talk