A new employee, five logins, three days of waiting: Prepare onboarding properly

The first day at work starts with a friendly welcome. The desk is clear, colleagues are there, the computer starts. Only the login doesn't work yet. A license is missing for the business application, there's no access to the project folder, and nobody knows which phone number was intended. So the new employee can only watch. Or uses a colleague's account.

Both are avoidable. Good IT onboarding doesn't start on Monday at nine o'clock, but with complete information before the person joins. The actual effort rarely occurs when setting up a single account. It occurs where nobody has decided what the new person needs.

First the role, then the permissions

"Please give them the same access as Ms. Müller" sounds practical. But it's not a clear description of the role. Ms. Müller may have accumulated additional rights over years, occasionally fills in for accounting or manages a special project. Whoever copies her profile unchecked copies that history too.

Better is a simple role overview. Which applications does the administrative team need? Which folders belong to case management? Who may approve invoices, share external files or access personnel records? Standard rights are defined per role, additional rights are approved separately.

This doesn't need to be an extensive organizational project. For a small business, a clear list of existing functions is often sufficient. What matters is that a person with subject matter responsibility confirms the selection. IT should not have to guess which client matters or business data someone may see.

A complete request avoids follow-up questions

For a prepared workplace, more than name and start date is needed. The request should include the correct spelling of the name, department, manager, work location, required devices and applications. This also includes shared mailboxes, groups, printers, telephony and, if applicable, remote access. Any temporary assignment should be clearly identified as such.

One person collects this information and passes it on in good time. HR knows the start date, the department knows the tasks, IT knows the technical requirements. If everyone assumes that someone else will take the last step, that step will be missing at the end.

Therefore also define by when changes must be reported. Hastily ordered specialized software can delay the start just as much as a missing notebook.

Account, licence and workstation are separate things

An existing user account does not mean that all services are usable. In Microsoft 365, users are created and required licenses are assigned. Which functions are available depends on the assigned products and services. Microsoft describes user creation and license assignment here.

In addition, a configured device is required: supported operating system, current updates, device protection, encryption and the intended applications. With an existing notebook, you don't simply change the previous owner's name. Old data and access must be handled after an orderly handover process before the device is redeployed.

Accessories are also part of preparation. A tested headset and a suitable display connector are more helpful on day one than a perfect order list whose delivery is still in transit.

The first login is part of the handover

The new employee should use their own account, not temporarily borrow someone else's. Multi-factor authentication or a suitable passkey is set up with guidance. This also clarifies which device or security key is intended for this purpose and how to request help if lost.

Access information is transferred via an agreed secure method. A permanent password in a group email is not a good shortcut. Equally, the login should not depend on an administrator's private phone just because it was available during preparation.

The handover includes a brief orientation: Where is shared data located? What doesn't belong in personal storage? Who helps with a suspicious email or locked access? These questions should be answered before work becomes urgent.

A workstation is not ready until the workflow has been tested

A checklist with green checkmarks is useful. What matters is whether the actual workflow works. For this, a short test with the new person is initially sufficient:

• Send an email and open the required shared mailbox.
• Open a designated document, edit it and save it in the correct location.
• Start the business application and check the appropriate role.
• Test telephony, Teams, printer and, if applicable, remote access.

Unnecessary permissions should stand out just as much as missing ones. After a few working days, a brief review follows: What is actually missing, what was granted as a precaution and is not needed?

Conclusion

Good onboarding is not a question of company size. It requires timely information, clear roles and a tested workstation. Then a new employee spends their first days on the actual task, not searching for access. And IT doesn't have to turn a foreseeable date into an emergency call-out.

Would you like to simplify your onboarding process? Schedule an appointment with shinpo IT.