Starting point: the same e-mail, two systems
The scenario takes place at a production plant where external companies have worked for years. A service technician of one of the contractors already had an account in the plant, created during an earlier job. Some time later he set up a professional profile in the contractor portal, where he collected his authorisations, training and medical checks, and from the portal he submitted a request for access to the same plant.
Both records use the same e-mail address. For a person this is obviously one and the same individual. For the system these are two independent identities: a local account in the plant and an identity in the portal. The question is who may link them, and on what basis, so that no second account is created and nobody takes over someone else's access.
Why the system does not link accounts by e-mail address
An e-mail address is easy to type, and in the portal it is not always proof of control of the mailbox at the moment of the request. For this reason, logging in with a portal account does not create accounts in the plant and does not match them by e-mail address. The account is bound to the person's identifier from the portal, and admitting someone onto the site remains the plant's decision.
For the same reason, approving a request with an address that already exists does not merge the accounts. The decision reads: approved, with instructions to log in with the portal account and confirm with a password. Until the contractor completes this step, nothing in the local account changes, and the access history stays assigned to the right person.
Parameters of the account link
Step by step: what the operator does and what the contractor does
The operator opens the request in the integration panel and sees the data the contractor agreed to share. The operator checks the company, the scope of work and the authorisations, and then approves. The system records that the e-mail address is already in the plant, and instead of creating an account it returns a decision with instructions to the portal. The contractor sees a message in the portal that he should log in to the plant with his portal account.
On first entry with the portal account, the contractor is taken to the regular password login. The password is proof that the local account belongs to him. After confirmation, the system shows a screen with the portal account that will be attached, and requires approval with a security token that protects against a forged request. The whole step must be completed within 180 seconds, because a pending link expires after that time.
- The operator approves the request and does not create a second account.
- The portal receives the decision with login instructions.
- The contractor logs in with the portal account and is taken to the password login.
- After password confirmation he sees the portal account to be attached.
- He approves within 180 seconds, after which later entries go through the portal.
Three safeguards of the link and what they give the coordinator
The link has three safeguards. First, the address from the portal must match the address of the account confirmed with the password. Second, a pending link expires after 180 seconds. Third, saving requires approval on the screen that shows which portal account is being attached. Each of them closes a different route of misuse: substituting someone else's address, leaving a session open, and clicking blindly.
For the coordinator this gives a simple rule for talking with the contractor: there is no need to ask for a change of address or to create a new account. It is enough to pass on the instruction from the decision. If the contractor does not remember the password, he uses the plant's standard procedure, not a workaround through the portal.
Result of the scenario and conclusions
The result shows in the operator's workload, not in seconds saved. No second account of one person is created, there is no manual merging of history, and there is no doubt about whom the permissions belong to. The operator makes one approval, and the burden of identity confirmation rests on the password that the plant already knows.
Conclusions: first, approve the request even when the e-mail address already exists, because this is the safe route with instructions. Second, prepare a short login guide for contractors covering the portal account. Third, remember that two-factor authentication and account blocks work exactly as with a password login, so an account disabled in the plant stays disabled when accessed through the portal.
Checklist
Video
Frequently asked questions
Will the system link the accounts if the e-mail address is identical?
No. The account is bound to the person's identifier from the portal, not to the address. The contractor confirms ownership of the account with a password.
What happens if the contractor does not finish within 180 seconds?
The pending link expires and the login has to start again. The data of the plant account does not change.
Can an account blocked in the plant get in through the portal?
No. Logging in through the portal goes through the plant's standard path, so accounts that are blocked, disabled, deleted or expired are rejected just as with a password.
Let's talk about the contractor portal at your plant
We will show you on a live example how a contractor's request reaches the operator and how the plant keeps full control over entry to the site.
Let's talk