The rule: the reader sends an event, not a template
An event from the access control system can consist of a person identifier and a timestamp. Nothing more is needed for working time records and permit systems. The biometric template serves only to recognise the person at the reader and should remain in the KD system.
The data minimisation principle in Article 5(1)(c) GDPR justifies this split: a further system receives only data adequate for its purpose. RCP has no reason to know the body features of an employee.
How InnerWeb receives events
InnerWeb is a software producer and integrates with the client's existing KD system. It does not manufacture or replace readers. It receives access events via webhook and links them with qualifications, permits, attendance and RCP, without taking over the role of the reader.
The platform provides a REST API secured with JWT and webhooks for automation. Ready-made connectors to specific client systems require implementation work, so the schedule must allow time for mapping fields on the KD vendor's side.
- the KD vendor configures sending of events to the webhook address
- the event contains the person identifier, a timestamp and the marker of the reader location
- the channel is authenticated with a JWT token
- biometric templates remain only in the KD system
Punch events per day depending on the number of employees, example
Implementation steps on the integrator's side
The sequence below reduces the risk that at launch it turns out the KD system sends more data than agreed.
Event specification
Before configuration starts, record the event fields and their meaning. The event must not contain a template field or a raw biometric measure, even if the KD system is able to send them.
Mapping of identifiers
The person identifier in KD must match the account identifier in InnerWeb. A mismatch causes events assigned to non-existent accounts or the lack of an alert about a missing training.
Test in a sandbox
Run punches on several test accounts, including a person without training, a person without a permit and a person using a card instead of a fingerprint. Verify in the log that the events have the same shape regardless of the identification method.
Review after go-live
After a few days, compare the list of punch locations in the log with the list of configured locations. A difference means readers that send events but are not covered by rules.
Pitfalls that appear most often
The first pitfall is exporting an overly broad KD record that incidentally includes a biometric field. The second is events from readers in unexpected locations that have no rules on the InnerWeb side. The third is manual punches entered into KD after a failure, which without a marked source look like a punch from a reader.
- extra fields in the event record
- readers in locations without rules
- manual punches without a marked source
- mismatched person identifiers
- device clocks out of step with the server
Example calculation: volume of events
With 800 employees and an average of 4 punches per person per day, this gives 3,200 events per day. These are illustrative assumptions that help estimate traffic on the webhook. An event containing an identifier and a timestamp is on the order of a few kilobytes, so the load on the channel is small.
What matters is the content, not the volume: 3,200 events without templates is a different risk profile from 3,200 records with biometric data.
Video
Frequently asked questions
Does InnerWeb require templates from the KD system?
No. An event with a person identifier and a timestamp is enough, and the templates stay in the KD system.
Does InnerWeb have ready-made connectors for every KD system?
The platform provides a REST API with JWT and webhooks. Connectors to specific client systems require implementation work.
Does changing a reader from biometric to card require changes in InnerWeb?
Usually not, because the event has the same shape. It is still worth checking the mapping of identifiers.
Sources
Let us agree the event specification
We will give the integrator a description of the punch event fields and the way the webhook is authenticated, so that templates never leave the KD system.
Let's talk