InnerWeb
Skip to main content

Guest QR badge alongside an access control card: recommendations for security

A security manager setting the badge policy usually has two worlds: proximity cards from an existing access control system and QR badges for guests and companies. They do not need to be mixed or swapped for one another. Below are the recommendations: who gets what, and a clear split of responsibility with the access control supplier.

Division of roles: a card for regulars, QR for visitors

A proximity card from the access control system suits people who come in every day: employees, permanent contractors, security staff. It is durable, the reader is mounted, and card management is in the hands of the access control supplier. A QR label suits people who come for one day or a few days: guests, drivers, service technicians, training participants.

InnerWeb is a software producer, not a maker of readers or access control cards. QR labels are printed on a label printer that the plant has bought and integrated, and the client's access control system stays unchanged. This matters for the budget: a QR policy for guests does not require replacing or extending access control.

Six recommendations for the badge policy

We have arranged the recommendations from the simplest decision to the most organisational one.

1. Divide the groups in the document, not at the gate

Record in the policy who gets an access control card and who gets a QR label. The gate guard should not make this decision again for each person. The criterion can be the frequency of entries or the length of stay.

2. Let the gate recognise both formats

Old proximity cards circulate as bare digit strings, and QR badges as an address with a token. The same recognition rule in the system handles both formats, so the gate scanner needs no separate procedures. A revoked card is rejected by the gate.

3. One code, several uses

The same code from the badge serves the gate, the invitation, checks in the hall and login to training. Scanning at the training tablet does not log in by itself: the screen shows whose code it is, and the training starts after a person confirms it.

4. Keep card events in the access control system

Card swipe events stay in the client's access control system. InnerWeb receives them from the access control system (webhook) and links them with qualifications, permits, attendance and working time recording, but does not replace the readers.

5. A guest badge has an expiry date in the process

A QR badge is linked to the invitation and the visit days. After the visit, security can revoke it, and the system issues a new token only at the next visit. A permanent employee's access control card gets an expiry date only on the access control system side.

6. Record the boundary of responsibility with the access control supplier

In the contract or the implementation note, separate the following: readers, cards and cryptographic keys are the responsibility of the access control supplier, while the software for guests, training and permits is the responsibility of InnerWeb. This way, when something fails, nobody has to hunt for someone to blame.

Who gets which badge (example split of policy points)

Who gets which badge (example split of policy points)Horizontal bar chart: three recommendations concern access control cards and three concern QR labels.0123policy pointsAccess control card (regulars)Access control card (regulars): 3 policy points3QR label (guests andcompanies)QR label (guests and companies): 3 policy points3
Source: Example calculation: split of the six recommendations on this page into those concerning access control cards and QR labels

Example of a policy entry for a production plant

At a corrugated board packaging plant, guests register by phone, the host has a role in the process, a health declaration required by BRCGS is signed at entry, and the secretariat receives the print order for QR labels. In such a setup the policy can fit on one page: employees and permanent contractors have access control cards, and everyone else has a QR label printed before arrival.

The guard then has two paths instead of ten exceptions. The QR label carries information about who invited the guest and for which days, so when asked whom the visitor is going to see, the answer is already in the system.

What this policy does not cover

A QR code on a paper or thermal label does not replace an encrypted card where high authentication security is required, for example for restricted areas. For such areas the plant uses encrypted cards from the access control system, and InnerWeb adds context: training, permits and attendance.

A QR label also has limited physical durability. If guests are to stay for weeks, consider a temporary card from the access control system instead of repeated prints.

Video

Frequently asked questions

Does a QR label replace access control cards?

No. It replaces them only for guests and companies on short stays. Encrypted cards from the access control system remain for daily visitors and for areas with a higher level of protection.

Does InnerWeb sell readers or cards?

No. InnerWeb is a software producer and integrates with the client's existing access control system.

Can the gate tell a card from a QR badge?

Yes. One recognition rule handles both formats, and a revoked card is rejected.

Where are card swipes recorded?

In the client's access control system. InnerWeb receives them from it and links them with qualifications and permits.

Build the badge policy together with security

We will go through the split between access control cards and QR labels with your security manager, and the boundary with the access control supplier. Book a call with InnerWeb.

Let's talk