Division of responsibilities
InnerWeb receives card tap events from the access control system through a webhook. It does not produce or replace readers, so on the integrator's side remains the configuration of the access control system, and on the InnerWeb side the linking of the event to a person, their qualifications and permits.
Reader events can be linked to qualifications, permits, presence and working time records. This means one card tap can feed several processes at once, provided the card identity is uniquely assigned to a person.
Step 1: agree the event contract
Start with a short contract document: which fields the access control system sends, what the time format is, and how the direction and control point are marked. At this stage we do not invent a format on request: the integrator describes what their system can send, and we map it to the event model.
The minimum we need to link an event is the card identifier, the event time and the control point identifier. The rest, for example the direction, helps with location but is not a condition for starting.
- Card identifier in a stable format.
- Event time with a time zone.
- Reader or control point identifier.
- Direction of entry or exit, if the system knows it.
Webhook integration stages and typical effort (example)
Step 2: assign cards to people
The webhook is useless without an assignment table: which card identifier belongs to which person. Assignments should come from one source, ideally the HR system or registration, and not from manual lists kept by the integrator.
Encrypted cards do not change this step, but they do change what is visible on the integration side: the identifier may be derived from a key managed in the access control system. What matters is that the identifier sent in the webhook is the same one stored in the assignment.
Lost and replacement cards
Block a lost card in the access control system, and keep the record in InnerWeb so that earlier events remain assigned to the right person.
Temporary cards
For guests and contractors, temporary cards require an explicit start and end of the assignment, otherwise the next people will inherit someone else's qualifications.
Step 3: security and reliability
The webhook should have authentication, for example a shared secret or a signature, and the source should be limited to the integrator's network. Transmission within the OT network must be agreed with the IT department, so plan it in advance and not on the day of go-live.
Events leaving InnerWeb for external systems go to an outbox queue, and delivery can be retried when the receiving system is temporarily unavailable. The same pattern is recommended on the access control system side: a queue with retries instead of a single attempt.
Step 4: acceptance test
The test starts with a single event from one test card, indicated by the client. Check that the event appears in InnerWeb against the right person and that the permit or presence status changes.
Then a load test: a series of events in a short time, for example a shift passing through the gate. At the end a failure test: a break in connectivity and delivery of the backlog after it is restored.
What to hand over to the client after acceptance
The client should receive short documentation: the contract, the flow diagram, the list of control points and a procedure for outages. Without it every reader replacement requires a new analysis.
Also record who owns the card assignments. This question comes back after a year, when the access control system supplier changes.
Checklist
Video
Frequently asked questions
Does InnerWeb supply card readers?
No. InnerWeb is a software maker and does not produce or replace readers.
Must the webhook come directly from the access control system?
We receive events from the access control system. An intermediary in the OT network is acceptable if it preserves the time and the card identifier.
What about backlogged events after an outage?
We recommend a retry queue on the access control side. On the InnerWeb side the same pattern applies to outgoing events.
What are the events used for after integration?
They are linked to qualifications, permits, presence and working time records.
Integrating access control with permits?
We will send the event contract and the list of questions to the access control supplier, and go through the acceptance test with you.
Let's talk