Scope of the integration and division of roles
InnerWeb is an independent supplementary system that works alongside the client's existing systems, including access control, RCP, HR and ERP. It does not replace them. It receives card punch events from the access control system through a webhook and links them with qualifications, permits, attendance and RCP. We do not supply cards or readers.
Before acceptance, write down on paper who is responsible for what: the access control vendor for events and readers, the IT department for the network and certificates, security for the procedures at the gate, and we for processing the events in the platform.
Events, identity and the queue
The first group of points concerns the event itself: whether it contains the person's identifier, the direction, the time and the access point, and whether the time is in a single time zone. The second group concerns reliability.
When the client's network blocks outgoing traffic from the application host, webhooks are stored permanently in a queue and collected by a poller through the incoming channel. Test this deliberately: block traffic for a few minutes, make punches, and check that all of them arrive after the block is lifted.
- The event contains the person's identifier, the direction, the time and the access point.
- Event times are consistent between access control and the supplementary system.
- Outgoing traffic block test: events enter the queue and arrive after the block is lifted.
- Duplicate events do not create double entries.
Acceptance checkpoints by group
Gate, training and permits
On the security screen, a scan of a QR badge or RFID card gives a verdict built from valid training, qualifications for hazardous work, a permit in progress and an active account, and the scan records the entry. When accepting the integration, check this on real test accounts.
On installations with entry cards, the training result is transferred to the account with the card, so that the gate stops reporting missing training. The system never merges accounts based on the surname alone, so in the test data use accounts that differ only in one field, and check that they are not merged wrongly.
When a worker without valid occupational safety training is scanned at the gate, the system creates an emergency permit and notifies the coordinator of the company. Calls are aggregated to one per company within a 55-minute window, so that security is not flooded with calls.
Privacy, language and proof of acceptance
The language of the account chosen at registration determines the language of the training. After a card or badge is recognised, the interface switches to the language of the person's account, so check this for at least two languages used in the plant.
The acceptance protocol should include screenshots from the tests and a list of edge cases: a lost card, a punch at the gate without training, no network. Such a document is evidence for an audit and saves disputes after a month of operation.
Checklist
Video
Frequently asked questions
Does the integration require replacing the access control readers?
No. InnerWeb integrates with the existing access control system and receives punch events through a webhook.
What if the network blocks outgoing traffic?
Webhooks are stored permanently in a queue and collected by a poller through the incoming channel. Events are not lost.
Will the system merge accounts by surname?
No. Accounts are never merged by surname alone, which reduces the risk of errors.
Let's prepare the acceptance together
We will deliver test scenarios for the gate, training and permits, together with an acceptance protocol. Book a conversation with the InnerWeb team.
Let's talk