Why a badge when the card is blocked
After a card block the employee still works, and their access to the gate must be ensured on a temporary basis. A QR code badge is an identifier for the time until a new card is issued. InnerWeb is a software producer, so label printers, scanners and cards are bought and integrated, while the badge itself comes from the system.
For the employee it matters that the code reveals no data. The badge token has 64 hexadecimal characters, comes from a random generator and is never derived from a counter, the person's number or the date, so it cannot be guessed from neighbouring badges.
Setting 1: the secretariat address
The secretariat address for label print requests is a system setting, empty by default. The option to order a print in the invitation is invisible until the administrator enters the address. This is the most common reason for asking why the print option is missing: it is not an error, only an unfilled setting.
Before go-live, decide which functional mailbox of the secretariat the requests should go to, and enter the address in the settings. Choose a functional address rather than a personal one, so that requests are not lost during someone's leave.
Bulk invitation limits
Setting 2: the printer and the label size
The first printing of the label of a person without a badge issues it automatically, and the print page matches the label to the size reported by the printer driver. This means the paper size in the driver must match the label roll in the printer.
The print page opened from the link in an e-mail sits behind the login to the security panel, because it contains badge tokens. The secretariat must therefore have an account with access to the security panel, and a link from an e-mail will not work for a person who is not logged in. Test this on the secretariat's account, not the administrator's.
Bulk requests and limits
For bulk invitations the print request e-mail goes out when all invitees have registered, or after 8 hours for those who did register. After 13 days the batch stops waiting. Bulk invitations are limited to 5 requests per 13 minutes per user and up to 144 addresses in one request.
In the card loss procedure bulk requests are rare, but the secretariat uses the same mechanism for guests and groups, so it is worth knowing the limits: a large influx of invitations should not block a request for an employee without a card.
Checklist before go-live
Run an end-to-end trial: a test employee without a card, a report, a print, a scan at the gate. Check whether the label fits the roll, whether the gate scanner reads the code and whether the ledger shows an entry with an active badge.
- the secretariat address entered in the system settings,
- a secretariat account with access to the security panel,
- the label size in the printer driver matching the roll,
- a print and gate scan test,
- information for the secretariat: one active badge per person.
Checklist
Video
Frequently asked questions
Why can I not see the print request option?
The secretariat address is a system setting, empty by default. Until the administrator enters it, the option is invisible.
Does the print link work without logging in?
No. The print page sits behind the login to the security panel, because it contains badge tokens.
How many badges can one person have?
One active badge. The rule is enforced in the application by a transaction lock.
Let's test badge printing at your plant
In a demo we will set the secretariat address and print a test label on your printer.
Let's talk