The boundary the system does not cross
Internal and privileged accounts, that is everything apart from an external company account with the external worker role, are never linked with guest or company invitations. This means that even if the e-mail from the guest list matches the address of a manager's or administrator's account, the system will not link the registration to that account.
The rule protects against one of the more dangerous scenarios: an outsider who types someone else's address into a form cannot take over or extend the privileges of a privileged account. For implementation it has a practical consequence: these two groups must not be treated as one list.
Why separate the lists
An administrator who combines lists of own employees and guests in one sheet multiplies the cases to resolve. A row that the system rejects as a conflict with an internal account must then be analysed separately. It is better to prepare two paths from the start: entering own employees, and invitations for external companies and guests.
Separating the list also makes assigning roles easier. An external worker gets a different scope than an own employee, so assigning a role in one step for the whole sheet increases the risk of error.
Split of 300 list rows in the example
Which entry paths the duplicate check covers
The duplicate check covers the invitation from the panel and registration from a QR code. Gate entry, quick adding of an employee, API, card swipe and tablet registration keep their existing checks. When planning a migration, you need to know which path a given group uses, because this determines which checks the system applies.
Guests and external companies
Outsiders most often enter by invitation from the panel or by QR code, which are paths covered by the duplicate check. This is good news for lists of large external companies.
Own employees
Own employees are sometimes entered by quick adding or through the API from the HR system. These paths keep their existing checks, so lists of own employees require tidying at the source before they reach the system.
Pitfalls and how to avoid them
The most common pitfall: a guest with the same e-mail as an internal account. The system will not link them, so such a registration will not take over the account, but it will be rejected or held back. The second pitfall: expecting the check to fix duplicates that already exist. The check works from the moment of deployment, not retroactively, and merging duplicates in production is a data change that requires a separate decision.
The third pitfall is confusing a role with an account. A person may work at the plant as an own employee and appear on an external company's list, for example when changing employer. In that case, before entry, it must be decided which account stays active.
- guest with an internal account e-mail: the system will not link the accounts,
- duplicates before deployment: merging needs a separate decision,
- change of employer: decide which account stays.
Recommended sequence in one migration
For a plant migrating both groups in one project, a three-stage sequence works well. First we enter internal accounts from the HR source. Then we invite external companies in batches. Finally we resolve the queue: weak matches, phone registrations and conflicts with internal accounts.
In an example calculation for a list of 300 people, in which 40 rows contain addresses matching internal accounts, these 40 rows go to manual analysis. The rest goes through the standard path.
Video
Frequently asked questions
Will a guest with an employee's e-mail be linked to their account?
No. Internal and privileged accounts are never linked with guest or company invitations.
Will the system fix duplicates we already have?
No, the check works from the moment of deployment. Merging existing duplicates is a data change that requires a separate decision.
Which registration paths are covered by the duplicate check?
The invitation from the panel and QR code registration. Gate, quick add, API, card swipe and tablet keep their existing checks.
Plan the migration of account groups
We will help you split the lists of own employees, external companies and guests and agree the order of entry. Book a talk.
Let's talk