InnerWeb
Skip to main content

FAQ: NFC app on the phone and questions from IT

IT hears the phrase 'identifier on the phone' and immediately asks about the app, certificates, device management and replacing readers. This page separates what in that chain belongs to InnerWeb, what belongs to the access control system vendor, and why the QR code opens in an ordinary browser.

Division of roles: who is responsible for what

The most common misunderstanding concerns who supplies the 'app for the doors'. A mobile identifier based on NFC, meaning a card stored in the phone wallet, is an element of the access control system and comes from its vendor: the vendor supplies the readers, the keys and the credential issuing service.

InnerWeb is a software producer, not a manufacturer of readers or access control cards. The system works alongside KD as an independent supplementary system that complements the client's existing systems: KD, working time recording, HR and ERP. For IT this means two separate paths, which are joined only by the tap event.

Questions about the app and installation

The first group of questions concerns what has to be installed and configured on the employees' phones.

Does InnerWeb require a mobile app?

No. A QR code scanned with the phone camera opens the plant address, and its token is passed to the training screen, which displays the identity confirmation. Everything happens in the browser, so there is no app store, no developer accounts and no update cycle on the phone side.

Does the phone need NFC?

Not for a QR code. A camera and a browser, which practically every phone has, are enough. NFC is needed only if the plant wants to use the KD vendor's mobile identifier in addition, and that is a decision made within the vendor's system.

Do the phones have to be managed through MDM?

A QR code requires no device policies or configuration profile, because nothing is installed. If the KD vendor requires a wallet app, that part falls under your device management rules and is worth discussing separately with the vendor.

Questions on this page by group

Questions on this page by groupBar chart: three questions each in the groups app, KD integration and code scanning0123questionsApp and installation: 3 questions3App and installationIntegration with KD: 3 questions3Integration with KDScan and recognition: 3 questions3Scan and recognition
Source: Number of questions in the sections of this page

Questions about integration with KD

The second group concerns what has to change in the existing infrastructure.

Do the readers have to be replaced?

No. A production plant with a KD system can deploy the QR code on the phone alongside the vendor's cards, without replacing any readers. Gates with card readers work as before, and the scan of the code is handled by the security panel or the reception desk.

How does the system learn about a card tap?

The KD system sends the identifier tap event to InnerWeb (a webhook), and InnerWeb links it with qualifications, permits, attendance and working time records. For the KD vendor we prepare an event specification, so that configuration on their side takes a short time.

Is GPS location required?

No. The system works as an independent supplementary system and does not need GPS for location. For access control, what matters is the event at the gate, not the position of the phone.

Questions about the scan and code recognition

The third group covers questions about security and reliability of reading.

How is the code scanned at the gate?

The security panel reads the code from a HID scanner, from a USB-COM scanner through the browser, and from a camera. All these paths feed the same recognition rule, so the plant can start with the equipment it already has and choose a scanner after the pilot.

Who decides what a scanned string is?

Whether a string is a token or a card number is decided by one rule on the server, shared with the gate. The browser does not parse the code, so IT maintains one place of logic instead of many versions on phones.

What about the token on the phone after system fixes?

Identity passes from the code to the training screen together with the token, so the training is recorded on the account of the code owner and not on an account entered by hand. For IT this is an important quality change, because training data no longer drifts between accounts.

What to prepare before the meeting with IT

Before the meeting, gather three pieces of information: the model of the KD system and the way it sends events, the scanners available at the gate, and the rules for browsers on employees' phones. With this set the pilot can be arranged in a single meeting, and the conversation with the KD vendor is limited to the event format.

Video

Frequently asked questions

Does InnerWeb replace the KD system?

No. InnerWeb integrates with the client's existing KD system and complements it with qualifications, permits, attendance and working time records. It does not produce or replace readers.

Will the QR code work on every phone?

On a phone with a camera and a browser, yes. For that reason it is worth testing a sample of the workforce's devices before the pilot, and we describe the method of the test in a separate guide.

Do we need a separate server on the plant side?

It depends on the chosen deployment model. With a QR code on the phone nothing is installed on the phone, and we settle the server architecture in a conversation about your IT requirements.

Who is responsible for the security of the keys in KD cards?

Management of the keys of cards and mobile identifiers belongs to the KD vendor and the plant's security department. InnerWeb does not store card keys.

Let us meet your IT department

We will show the flow of the QR code and of KD events on an example plant, and prepare a specification for the vendor of your KD system.

Let's talk