InnerWeb
Skip to main content

FAQ: strong and weak account matching in the system

The system administrator wants to know when a registration will be linked to an existing account, when the system will ask a person, and when it will refuse. The answer depends on what the match was based on: an identifier that clearly points to one person, or only a first and last name.

3
maximum number of candidates a person sees for a weak match
Source: duplicate detection feature sheet
780 s
validity of the decision token
Source: duplicate detection feature sheet

How the system recognises the same person

Strong matching relies on data that points to one person: an e-mail address, a phone number in E.164 format, an employee number or an external login identifier. Weak matching relies on the first and last name, compared regardless of letter case and diacritical marks.

The difference has a practical effect. A match on an e-mail address is rarely a coincidence, while a match on a surname may concern two different people, so the system treats them differently.

  • Strong: e-mail, phone in E.164, employee number, external login identifier.
  • Weak: first and last name, regardless of letter case and Polish characters.

When the system links an account on its own

A strong match on an e-mail address to an active account that has no password and no login identifier connects the registration to the existing account. This is the typical case of a person created earlier at the gate who later registers from a QR code with the same address.

The other strong matches end with a 409 response: an account with a password, a pending invitation and a deleted account. A deleted account is never restored, so a person who was once deleted does not come back through registration.

Decision parameters for a weak match

Decision parameters for a weak matchHorizontal bar chart: at most 3 candidates, token valid for 13 minutes, which is 780 seconds.0200400600800valueCandidates (max.)Candidates (max.): 3 value3Token validity (min)Token validity (min): 13 value13Token validity (s)Token validity (s): 780 value780
Source: Customer account duplicate detection feature sheet; 780 s = 13 min

When the system asks a person

A weak match does not link accounts on its own. A person decides, and the system shows at most 3 candidates with a masked e-mail address and phone number, so that it does not reveal the data of someone who may be a different person. The decision token is valid for 780 seconds, which is 13 minutes.

A match based only on a phone number from the public form leads to waiting for approval by the administrator and changes nothing on the account, because phone numbers are not verified. The administrator sees the request and decides.

Which accounts the system protects from being linked

Internal and privileged accounts, meaning everything except an account of an external company with the external worker role, are never linked from guest or company invitations. A registration from a poster therefore cannot take over the account of an OHS department employee or an administrator.

Duplicate control covers invitations sent from the panel and registration from a QR code. The gate, quick adding of an employee, the API, card scanning and registration on a tablet keep their existing checks.

The incident behind these rules

In production the same person had two accounts: one created at the gate without an e-mail address, the other six minutes later from a QR poster, and the person completed the training twice. The lack of an e-mail address at the gate prevented a strong match, and a match on the name requires a human decision.

The conclusion for the administrator: at the gate it is worth collecting an e-mail address or an employee number, because each of them turns a later weak match into a strong one.

What about duplicates that already exist

Control works from the moment of deployment, not retroactively. Merging duplicates that already exist in production is a change to data and requires a separate decision, with a backup and proof of execution. When migrating from a spreadsheet, this means the list of people is cleaned before loading, not after.

Video

Frequently asked questions

Will the system link an account by surname alone?

No. A weak match on the first and last name requires a person to choose from at most 3 candidates with masked data.

What happens when a person registers with an account that has a password?

The system responds with 409 and does not link the accounts. Automatic linking applies only to an active account without a password and without a login identifier.

Is a phone number enough for linking?

No, when it comes from the public form. The registration goes to the administrator for approval, because phone numbers are not verified.

Can a deleted account come back through registration?

No. A deleted account is never restored, and the registration ends with a 409 response.

Want to see account matching in a demo?

We will show QR code registration, strong and weak matching, and the administrator decision screen.

Let's talk