Why you need a procedure

In a small business, onboarding a new employee sometimes looks like this: the day before they arrive, someone remembers that a computer is needed, the technician is asked to “set up a user just like the senior employee’s,” and the new hire gets every permission the senior employee has collected over the years. Everything works, and nobody knows exactly why the employee has access to the payroll folder.

A short, fixed procedure solves this. It saves time on day one, prevents unnecessary permissions and gives the business a clear picture of who can access which information. When an employee leaves (offboarding), the same procedure runs in reverse, and that is exactly where many businesses fall short: active accounts of employees who have left (orphaned accounts) are one of the most common weak points in organizations.

Before day one

It all starts with an organized request from the direct manager, a few days before the start date. It does not have to be complicated, but it should include:

  • Name, role, department and start date.
  • Which systems and folders the employee needs to access, based on the role.
  • What equipment is needed: laptop or desktop, monitor, phone, headset.
  • Whether working from home or remote access is required.
  • Professional software and special licenses.

When the request arrives in advance, the IT provider prepares everything on time, and the employee starts working on day one instead of waiting hours for a username and password. The request itself is kept, and that is already the start of documentation.

User account, email and permissions

The employee’s user account, in Active Directory, Microsoft Entra ID or Google Workspace, is the key to everything else. It is worth building permissions around role groups (RBAC): an accounting employee joins the accounting group and gets what the group gets. That way you never copy permissions from another user, and when the role changes you simply switch groups.

The guiding principle is least privilege: the employee gets access to what the role requires, not to everything possible. In addition:

  • Multi-factor authentication (MFA) is set up on day one, before the employee starts using email.
  • A temporary initial password that the employee changes at first sign-in.
  • Access to shared mailboxes and calendars through the personal user account, instead of a shared mailbox password.
  • No administrator rights for a regular employee, even if it is “more convenient.”

The same logic applies to a change of role. An employee who moves from sales to accounting should leave the previous groups when joining the new ones. Otherwise permissions pile up (privilege creep), and after a few years the employee has access to almost everything. A periodic access review, in which each manager confirms who on their team sees what, catches this buildup before it becomes a problem.

Preparing the computer

A computer prepared from a fixed template (baseline) causes fewer problems and is easier to support. Such a template should include:

  • Disk encryption, for example BitLocker, so that a stolen laptop does not expose the data on it.
  • EDR protection that reports to a managed system someone actually monitors.
  • Automatic updates (patch management) for the operating system and applications.
  • Local administrator password management with LAPS, with no administrator rights for the user.
  • Enrollment in the management system: a domain, Intune or an equivalent system, so policy can be enforced and the computer can be locked remotely.

If the employee receives a company phone, or uses a personal phone for company email, the phone also needs to be managed (MDM): screen lock, system updates and the ability to remotely wipe the business data (selective wipe) if the device is lost, without touching the employee’s personal content.

Every device is recorded in the business’s equipment list (asset inventory), with its serial number and the name of the employee who received it. This list will be used again on the day the employee leaves, and also when planning equipment replacement.

Software and licensing

Software is installed from an approved version and under the business’s license. Software that employees download on their own, unknown browser extensions and personal accounts on cloud services (shadow IT) are a common source of data leaks and licensing problems. A license opened under an employee’s personal name leaves with them when they go, together with the files saved in it.

The same is true for AI tools (shadow AI). If the business allows them, it should decide which tools and which account may be used, and which types of information must never be entered into them. That decision should be made once at the business level, not again for each employee.

The first day

Half an hour of organized explanation on the first day goes a long way. No lecture is needed; covering a few points is enough:

  • Where to save files, and why not on the desktop.
  • How to recognize a suspicious email (phishing) and whom to report it to.
  • How to open a support ticket.
  • What is and is not allowed when using equipment, email and external tools.

The employee should sign an acceptable use policy and a confidentiality agreement (NDA). This is also the time to make clear that reporting a mistake, such as clicking a suspicious link, is welcome and not a reason for a reprimand.

In a business that hires often, it is worth turning the explanation into a short page or an internal video, so every employee gets the same information regardless of who onboarded them.

Privacy and documentation

If the employee accesses personal information about customers, employees or patients, onboarding is also a regulatory matter. The Privacy Protection Regulations (Data Security) require, among other things, managing and documenting permissions to databases and training those who receive access to them. Since Amendment 13 to the Privacy Protection Law came into force in August 2025, the Privacy Protection Authority has broader enforcement powers, including administrative fines. Organized documentation is how the business shows that it meets the requirements.

In practice, a documented onboarding and offboarding procedure is a large part of the answer. An IT provider who knows the requirements will build it so that the documentation is created as the work is done, not as a separate task someone remembers before an audit. This is one of the reasons the business’s IT provider has to understand regulation no less than equipment.

When an employee leaves (offboarding)

Leaving is the more sensitive moment. An employee who has left and still has access to email, folders or the CRM system is a real risk, even when the parting is friendly. The procedure should be carried out on the last day, and in sensitive cases even earlier:

  • Disabling the user account and ending all active connections (session revocation), including on the phone.
  • Removing the MFA methods registered in the employee’s name.
  • Transferring email and files to the replacement or the manager.
  • Collecting equipment according to the equipment list.
  • Changing shared passwords the employee knew, if any still exist.
  • Removal from external systems: suppliers, government websites, banks and advertising platforms.

When the departure is not by mutual agreement, coordinate with the IT provider in advance, so access is closed exactly at the time of the termination meeting and not several hours later.

Summary checklist

  1. There is a standard request form that the manager fills out before onboarding.
  2. Permissions are granted by role groups (RBAC).
  3. Multi-factor authentication (MFA) is set up on day one.
  4. The computer is prepared from a template: encryption, EDR, updates and central management.
  5. The employee received a short briefing and signed an acceptable use policy.
  6. Permissions and equipment are documented.
  7. There is an offboarding procedure that is carried out on the last day.

If some of these items are not in place yet, start with the offboarding procedure and a check of active accounts belonging to employees who are no longer with the business.