Skip to main content
Legia

IT Support & Consulting

IT Onboarding for New Employees: Devices, Accounts, and Access on Day One

Orderly IT onboarding lets new employees work from day one, and later turns offboarding into simply reversing the record. This checklist covers accounts, devices, and role-based access.

SEO and Content Specialist

5 min read

Two people discussing in front of laptops and notes

Short answer: IT onboarding for a new employee covers five things prepared before day one: a personal account (not a shared one), a recorded device in the user’s name, application access based on role, multi-factor authentication for email and remote access, and an introduction to basic security rules. Every access granted is recorded in one list, so that when the employee changes department or leaves, the access can be revoked completely.

A new employee’s first day is often spent waiting: the laptop is not ready, the email account has not been created, and application access is requested one by one through messages to colleagues. The problem is not only wasted time. Access granted in a hurry tends to be excessive and unrecorded, and unrecorded access is access that gets forgotten when the employee leaves. Orderly IT onboarding for new employees solves both at once.

This article is the counterpart of IT Offboarding Procedure: Revoking Access for Departing Employees. The order is deliberately parallel: what is granted here is what is revoked there.

Why IT onboarding shapes security

The CIS Controls v8.1 security framework treats both of these as basic controls. Safeguard 6.1 asks organizations to establish and follow a process for granting access when a new employee joins, when rights are added, or when a role changes. Safeguard 5.1 asks for an inventory of all accounts that records at least the owner’s name, username, start and stop dates, and department. The NIST Cybersecurity Framework (CSF 2.0) says something similar: access permissions are defined in a policy, managed, reviewed, and follow the principle of least privilege.

In other words, onboarding is not just a matter of convenience. It is the starting point of the whole access record that is later used to review and revoke it.

Illustration: IT support

IT onboarding checklist

AreaWhat to prepare
Main accountCreate a personal email and directory account, with a unique initial password that must be changed at first login
AuthenticationEnable multi-factor authentication for email, internet-facing applications, and remote access
ApplicationsGrant application access according to the list for the role, not by copying another employee’s access
Remote accessCreate a VPN or remote access account only if the role needs it
Privileged accountsIf the role needs admin rights, create an admin account separate from the everyday account
DevicesPrepare a company laptop or phone, record its serial number and user, and install standard applications
DataPoint file storage to shared folders or company-owned services
LicensesAllocate the required licenses and record who uses them
Record keepingRecord every account, access, device, and license with its date in one list

Access by role, not by copying a colleague

The most common habit is asking IT to “just give them the same access as A”. It is fast, but it also copies every access A has collected over the years, including what is no longer relevant. CIS Controls Safeguard 6.8 suggests a tidier approach: define and document the access each role needs, then review it regularly, at least once a year.

For a mid-sized company, the role list does not need to be complicated. Start with a few main roles, for example finance staff, sales staff, operations staff, and system admins, then write down which applications and folders each one needs. Access outside that list is requested through the official channel and approved by the manager.

Two additional CIS Controls rules that are easy to apply from day one:

  • Separate admin accounts (Safeguard 5.4): everyday work such as email and web browsing is done from a standard account, with admin rights only on a dedicated account.
  • Unique passwords (Safeguard 5.2): at least 8 characters for accounts using multi-factor authentication and 14 characters for those that do not.

Split of duties between HR, managers, and IT

As with offboarding, onboarding runs smoothly when the duties are clear:

  • HR notifies IT as soon as the start date, name, job title, and department are confirmed, not on the first day.
  • The direct manager states the role and the applications needed, including departmental applications not managed by central IT.
  • IT prepares accounts, devices, and access according to the role list, then records everything.

The order from before joining to the first week

  1. As soon as the start date is confirmed: HR sends the employee’s details to IT, and the manager confirms the role.
  2. Before day one: prepare the device, create accounts, allocate licenses, and grant access according to the role.
  3. Day one: hand over the device with a signed receipt, ask the employee to change the initial password and enable multi-factor authentication, then explain the channel for requesting IT help.
  4. First week: give an introduction to security rules, for example spotting fraudulent emails and how to report incidents. CIS Controls Safeguard 14.1 requires security training at hire and at least once a year.
  5. End of the first week: the manager confirms that the access is sufficient, neither too little nor too much. Accounts that were created but never used are disabled.

Common mistakes

  • A shared account for new employees “while waiting for their own account”. Accounts like this are rarely actually shut down.
  • The same initial password for every new employee, or one sent through a message others can easily read.
  • Devices handed over without a record, so when the employee leaves it is unclear which device must be returned. How to build that list is covered in IT Asset and Software License Inventory: How to Build One.
  • Changing department without revoking old access. A role change is best treated as onboarding into the new role and offboarding from the old one at the same time.

How Legia does it

In the IT Support & Infrastructure Management service, Legia handles employees’ daily requests, work devices, and accounts, including email accounts and shared workspaces managed in your company’s name. All requests come in through one ticketed channel, so the status and handling history for every new employee can be traced. All accounts stay in your company’s name, and when an employee leaves, the access recorded since onboarding is what gets revoked and then documented. Other services in the same area are on the IT Support & Consulting page.

Frequently asked questions

What about contract staff, interns, or vendors?

The same process applies, with an end date recorded when the account is created. For vendors, access should use accounts you issue, not a shared account owned by the vendor.

Can new employees use their personal laptops?

Yes, if a personal device policy is in place. Company data should still be stored in company-owned services, so access can be revoked centrally when the employee leaves.

Who approves additional access after day one?

The direct manager, through an official, recorded request channel. Approvals sent through private messages are hard to trace when the access needs to be reviewed or revoked.

Sources

Category IT Support & Consulting

Keep reading

Related articles

All Articles