InnerWeb
Skip to main content

Duplicate accounts and card: no training at the gate

The employee passed the training, yet the gate still reports that training is missing. On one installation with a card import, a measurement found 47 pairs of duplicate accounts, and 46 of them were merged. We describe the cause, the matching threshold and the procedure that a security manager can repeat at their own site.

47
duplicate account pairs on one installation
Source: karta
46
pairs merged after verification
Source: karta
45 → 0
alarm candidates after narrowing
Source: karta

Symptom: valid training, yet the gate says no

The security manager reports the same picture several times a week: a contractor's employee shows an induction certificate, while the reader at the gate displays a missing valid training. The guard has no tools to settle the dispute, so the person waits and the queue grows when the crews change shifts.

The first hypothesis is usually an expiry date or an operator error. In the case described, both turned out to be false. The training was passed, the expiry date was valid and the result was recorded correctly. The problem was that the result had been saved to a different account of the same person than the one to which the card was assigned.

Cause: two active accounts of one person

When one person has two active accounts, the training result can land on the account without a card, while the account with the card still reports the missing training at the gate. The second copy usually appears during a card import from a list supplied by an external company: a surname spelled differently, a first name and surname swapped or a missing diacritic is enough for the system to create a new account.

This is why the correctness of the training alone is not enough. The gate reads the account linked to the card number, while the training was completed by someone who logged in to an account created earlier, from a different invitation. For a human this is one person, for the system these are two different identities.

Prevention is possible already at the training stage. The variant with RFID cards in the trainings lets the person tap the card and select their own account, or remotely select the company and type a fragment of the first or last name. The search requires at least 3 characters after text normalisation, returns at most 13 results, shows only active accounts with an active card assignment, and does not reveal the card number or the full list of employees. After a result is selected, the training is recorded on the existing account with the card, not on a new one. The variant is enabled by a configuration flag, so it is an option that the installation can request.

Duplicate account pairs on one installation

Duplicate account pairs on one installationBars: 47 pairs detected and 46 merged.01020304050parDetected: 47 par47 parDetectedMerged: 46 par46 parMerged
Source: Measurement on one installation with a card import

Measurement: 47 pairs, 46 merged

On one installation with a card import, 47 pairs of duplicate accounts were counted. After verification, 46 of them were merged. An alarm that searches every day for pairs where the training result sits on an account without a card dropped the number of candidates from 45 to 0 once the search was narrowed to these cases. The target value of such an alarm is 0 pairs.

The value of the measurement for a practitioner is twofold. First, the scale: almost every pair required a separate decision, not a mass operation. Second, one pair was left unmerged because it needed a decision made by a person. This shows that the procedure should leave exceptions for manual assessment, rather than force a zero result at any cost.

  • duplicate account pairs: 47
  • pairs merged after verification: 46
  • alarm candidates before narrowing: 45, after narrowing: 0

Why we do not merge automatically by surname

The system never merges or redirects an active account based on the surname alone. The reason is practical: people from one crew are sometimes related or have similar surnames, and they could be confused, and a mistake means that someone receives someone else's permissions.

The similarity threshold was chosen on the basis of a measurement, not a hunch. True pairs scored from about 83, different people from one company at most about 74, but brothers also about 83. This last value settles the matter: the matching score alone is not enough for automatic merging, because it does not distinguish a brother from the same person.

The Is this you list that the employee sees shows the account with the card first, and the matching also covers swapped first and last names. As a result, the choice is made by a person who knows their own data, not by an algorithm guessing for them.

Name similarity score

Name similarity scoreBars: true pairs from 83, different people up to 74, brothers about 83.020406080100pointsTrue pair (from): 83 points83 pointsTrue pair (from)Different people (up to): 74 points74 pointsDifferent people (up to)Brothers: 83 points83 pointsBrothers
Source: Measurement of the similarity threshold

Merge procedure step by step

A pair of accounts is merged by a person running a command with a preview mode before execution. The command refuses when the accounts belong to different companies, when one of them is an administrator account, or when the source is an account with a card. The preview mode shows what will be changed before anything happens.

In a merge, the better training result is moved to the account with the card, and the account without a card is marked as deleted with a reference to the target account, without deleting any data. A trail remains for the audit, and any mistake can be reversed.

The order for the security manager is simple: run the pair alarm, select a pair, review the preview, approve, check the card tap at the gate, and close the ticket. The whole process should take a few minutes per pair, not an hour of discussions between security, HR and the external company.

Conclusions for security and IT

The card import into the system is the moment when duplicates are easiest to introduce, so the check of pairs should be a permanent step after every import, not a reaction to a complaint at the gate. One daily alarm costs less than a stopped employee and a guard's intervention.

InnerWeb works here as a complementary system: it does not replace readers and does not change the access control system. It only links the account, the card and the qualifications so that the training result is located where the gate reads it.

Video

Frequently asked questions

Why is an employee with training stopped at the gate?

The training result may have been saved to another account of the same person that has no card assigned. The gate reads the account with the card, so it reports missing training even though it was passed.

Does the system merge accounts automatically by surname?

No. The surname alone is not enough, because people from one crew may be related. The merge is performed by a person using a command with a preview.

Does the merge delete the data of the account without a card?

No. The account is marked as deleted with a reference to the target account, and the better training result is moved to the account with the card.

How many duplicate accounts can be expected after an import?

On one measured installation there were 47 pairs. The value depends on the quality of the input list, which is why it is worth counting the pairs after every import.

Sources

Check account pairs after a card import

We will show the duplicate account alarm on your import data and go through the merge procedure with security and IT.

Let's talk