Starting point: one day, many accounts, one e-mail per person
A typical wave looks like this: the HR department of a production plant has dozens of new accounts to enter into the system in a single day. Invitations must arrive before the first shift, and each person has to complete the induction training and set their own password before appearing on site.
In the InnerWeb system an invitation creates an inactive account with an empty password and sends one e-mail with one activation link. The person receives no login and no temporary password. The whole process rests on clicking that single link, so how the link behaves decides whether everyone in the wave reaches the system in the same state.
There is no mass-import function for invitations. Mass entry is a loop: create an account, send the invitation, create the next account. As a rough guide it takes about 2 seconds per account, so 40 accounts means about 80 seconds of loop time, not counting the preparation of the list of people.
Path for accounts with training available
If a mandatory training is waiting on the account, the link from the invitation leads to the training first, and the password is set only after it is completed. If there is no training, the link goes straight to setting the password. This order is intentional: nobody gets a working account before learning the security rules that apply at the plant.
The matching works without any operator action when an active mandatory training exists in the language of the account. For accounts in Polish this is usually the Polish-language training, so that group follows the path as designed.
- the invitation creates an inactive account with an empty password
- the link leads to training if one is waiting on the account
- the password is set after the training, not before it
- after the password is set the system logs the person in automatically
Loop time for invitations at 2 s per account
Checkpoint: account languages and training availability
The mandatory training is matched by the language of the account. When only the Polish training is active, an account in another language has no induction training assigned and goes straight to setting the password without it. The system reports no error at this point, because from its perspective there is nothing to run.
That is why, before a wave, you need to check which languages the accounts will use and make sure active material exists for each of them. This matters most for foreign workers, who often work in roles where the introductory briefing is most important and where the language barrier makes it harder to catch up during the first days.
This checkpoint takes a few minutes and saves manual retraining after the fact. A good practice is to create one test account per language and walk the whole path to the end before sending the real invitations.
Why a missing training is not visible in the account list
An account without induction training looks in the system exactly like an account that completed it: it has a password set, it is active and it can be logged into. The only difference is the missing training result, and nobody checks that during a routine review of the user list.
For this reason the check should be a separate task, not a side effect of the invitations. After the wave, compare the list of invited people with the list of people who have a recorded induction training result, and split it by account language. A gap in one language points straight to the missing material.
Recommendations for HR before each wave
The first recommendation concerns the order of work. Before the first invitation is sent, check the languages of the accounts and the active mandatory trainings for each of them.
The second recommendation is a sample. The activation token stays valid for 7 days, and simply opening the link does not use it up, so the link can be checked safely before anything goes to people. Set up one test account per language, send an invitation and walk the path to the end.
The third recommendation is to close out the wave: the list of invited people, the list with a training result, the list without a password and a short note on discrepancies. This set takes half an hour and gives audit evidence that each person went through the induction training, or that a gap was found and closed.
- check the account languages before sending
- make sure a training exists for each language
- send trial invitations to test accounts
- after the wave, prepare a list of invitees with training results
Loop time for one wave of invitations
| Parameter | Value |
|---|---|
| Number of accounts in the wave | 40 accounts |
| Time per account | 2 s |
Result: 40 x 2 s = 80 s of loop time, about a minute and a half.
Note: Sample calculation. It does not include preparing the list of people or the check after sending.
Checklist
Video
Frequently asked questions
Does the system warn when an account has no assigned training?
No. For the system, the absence of a training for the account language means there is no step to run, so the person goes straight to setting the password. Detecting the gap requires comparing the list of invitees with the training results.
Is there a mass invitation import from a file?
There is no mass import function. Mass entry is a loop of creating an account and sending the invitation, roughly 2 seconds per account.
How long is the invitation link valid?
The activation token stays valid for 7 days, and simply opening the link does not use it up. The link can therefore be checked before it is sent to employees.
What should be done with accounts that went through without training?
Activate a mandatory training for the language of those accounts and take those people through it separately. Record the discrepancy and its closure in the wave summary.
Plan your next wave of invitations
Let's talk about setting up induction training in the languages of your employees and about checking the results after the invitations are sent.
Let's talk