Skip to content

Blog

IT onboarding checklist for new hires

An IT onboarding checklist for new hires: accounts set by role, an encrypted laptop, two-step verification and a first-week access check, step by step.

· 9 min read

An IT onboarding checklist covers four things to have ready before a new hire's first morning: their accounts, set to the right role in each tool; a laptop that is encrypted, updated and enrolled; the security basics, such as two-step verification and a password manager; and a check at the end of week one that all of it works and nothing extra was given. Below, every step is a short paragraph with a bold lead-in, grouped by when it happens, so you can copy the whole thing into a ticket or a doc.

This one is written for whoever sets up accounts and devices: the office manager, the operations lead, the engineer who drew the short straw. The HR side of onboarding (contracts, payroll, the welcome lunch) is in the employee onboarding checklist. This is the part where someone needs a working laptop and fifteen logins.

Before day one

Most first-day IT problems are really problems from the week before. The fix is to start the moment the offer is signed, not the Friday before the start date.

When the offer is signed

Get the start date and the location. Whether they start remote or in the office decides when the laptop has to ship, and a laptop in a courier depot on day one is a lost day.

Get the role and the team. These decide which tools they get. "Engineer" is enough to start; "Engineer, joining the payments team" is better, because the team decides the channels, repositories and folders.

Get the manager's name. The manager approves anything unusual, and is the person you ask on day three when something is missing.

Get the contract type. Employee or contractor. A contractor usually gets fewer tools, a fixed end date, and sometimes no company laptop at all. Contractor access management covers that case in full, and there is a short version further down.

Order or prepare the laptop. A reused machine needs wiping and reinstalling, which takes longer than you expect. Never hand over a previous person's laptop with their user profile still on it.

Two to five days before the start date

Create the main account. In Google Workspace or Microsoft 365, a few days ahead. Put them in the right organizational unit and groups straight away, because groups often grant shared drives, calendars and mailing lists without any further work.

Hold the other tools until the main account exists. Most invites go to the work email, and many tools let people sign in with Google. Inviting a personal address now creates an account you will have to find and remove later, and it is the most common source of the unknown accounts that turn up in every user access review.

Send the role's invites. Two to five days is the right window. Earlier, and some invites expire or the offer falls through. Later, and day one is spent waiting for emails. If the start date moves, move the invites with it.

Decide how the first password reaches them. Not in the same email as the username. Many teams hand it over on the first call, set to change at first sign-in.

Accounts by role

Every new hire gets the baseline: email, calendar, chat, video calls, the password manager, the HR portal. After that, access should follow the role, not the request of whoever is loudest in the hiring channel. Two rules keep this clean.

Pick the role inside each tool, not just the account. Creating the account is half the job. In Slack the choices run from Workspace Owner and Workspace Admin down to full member and guest. In a GitHub organization a person can be an owner, a member, a billing manager or an outside collaborator, and on each repository anything from Read to Admin, per GitHub's documentation as we read it on 27 October 2026. A new hire almost always wants the plain member role. "Admin for now" is how admin lists grow.

Write the role down once, then reuse it. If you have hired two engineers, you already know what the third needs. Put it in a table: role, tools, and the role inside each tool. Role-based access control explains how to draw that table for a small company, and the hub post on user provisioning shows an example set of bundles.

The access people forget

Some access is easy to miss because it is not a "tool" with a login page.

Groups and shared inboxes. Addresses such as support@ and billing@ are usually Google Groups or delegated mailboxes. A support hire who is not in support@ cannot do the job.

Shared drives and link-shared folders. Shared drives follow group membership; folders shared "by link" do not, and someone has to send the link.

Password manager vaults. The vault or collection for their team, which holds the logins nobody has put behind a proper account yet.

Cloud consoles and production. Grant these on purpose, when the work needs them, and record who approved it. They should never arrive by default with the welcome pack.

Recurring meetings. The calendar invites for standups and team meetings. Not a security item, but the first thing a new hire notices is missing.

Contractors and other edge cases

Contractors change the maths in tools that bill by seat. In Slack, multi-channel guests are "billed as regular members", while single-channel guests are free, up to five per paid active member, and owners and admins can set a guest to deactivate automatically on a date, according to Slack's guest help article as we read it on 27 October 2026. Set that date when you invite them; it is the cheapest offboarding you will ever do. In GitHub, "adding an outside collaborator to a private repository will use one of your paid licenses" on any paid plan, per GitHub's docs on outside collaborators, read the same day.

A rehire is another edge case. Before creating anything, search for their old accounts. Some tools will still have them, sometimes with their old role, and reactivating the wrong one hands back access from a job they no longer do.

Devices

A laptop is ready when it is safe to lose. Do these before it ships.

Turn on full-disk encryption. FileVault on a Mac, BitLocker on Windows. A stolen encrypted laptop is a hardware cost; an unencrypted one is a data incident.

Update the operating system and leave automatic updates on.

Enroll it in device management, if you use it. Device management (often called MDM, mobile device management) lets you enforce settings, push apps, and lock or wipe the machine remotely. If you do not use it, write down the serial number and who has it. That is the minimum.

Give them a standard user account, not a local administrator. Most people do not need to install drivers. Those who do can ask, and the request leaves a trace.

Set a screen lock after a few minutes idle, with a password.

Install the usual apps: browser, chat, video calls, the password manager. Anything else they can request.

Decide the phone rule once. Are company email and chat allowed on personal phones, and if so, what is required (a screen lock at least)? Write that down once and stop deciding it per person.

Security setup on day one

These steps are quick on day one and tedious to retrofit later.

Hand over the first password and require a change at first sign-in.

Turn on two-step verification on the main account. In Google Workspace you can enforce it for everyone and give new accounts a New user enrollment period, a window from 1 day to 6 months in which they can sign in with just a password and set up their second step, according to Google's 2-Step Verification guide as we read it on 27 October 2026. Keep the window short. A day or two is enough for someone sitting at a laptop with you.

Set up the password manager, with a strong master password, and give a quick tour of the shared vaults they now have.

Add recovery details to the main account: a phone number or recovery method that is theirs, not the previous hire's.

Grant no admin rights by default, in the operating system or in any tool. Admin is granted for a reason and recorded. The principle of least privilege has the longer argument.

Spend five minutes on phishing. Show what a fake "your password expires" email looks like, and say who to ask when unsure. New hires get targeted because they do not yet know what normal looks like. The Google Workspace security checklist covers the account-level settings that back this up.

First-week check

On day five, sit down with the new hire for fifteen minutes and go through their access.

Confirm they can get into everything they need. Invites expire, land in spam, or go to the wrong address.

Remove anything they do not need. Do it now, while it is fresh. It is much harder to remove access a year later, when nobody remembers why it was given.

Check that two-step verification is actually on. Enforcement with an enrollment window means it can still be off.

Check the laptop is reporting in, encrypted and updated.

Record what they have. Tool, role, date. This record is what makes their offboarding quick, whenever it comes.

How the checklist changes with company size

At five people, the checklist is a note in a shared doc and the founder runs it. Most of the value is in two habits: invite to the work email only, and write down what was given. Skip device management if you have three laptops; keep the serial numbers.

At twenty people, the same person can no longer remember who has what. That is when role bundles stop being a nice idea and start saving real time, and when "admin for now" starts showing up in the review.

At fifty, onboarding happens most weeks, often with two people starting the same Monday. The checklist needs an owner, a ticket per hire, and a named approver for paid seats. Device management usually earns its cost here, if it has not already.

Common mistakes

The same few mistakes cause most first-week trouble. Inviting a personal address because the work account was not ready yet. Giving admin rights to save a support request. Sending the username and password in one email. Reusing a laptop without wiping it. And the quietest one: never doing the day-five check, so nothing extra is ever removed and nothing is ever recorded.

If you do one thing this week, write the role table for the job you hire most often. The next joiner in that role is then a matter of working down a list, not remembering.

Where SmashSSO fits

SmashSSO takes the "send the role's invites" step off this checklist. It reads your people from Google Workspace. You define access bundles by role, such as "Engineer", and assigning one invites the new hire to every tool in it with the right role inside each. Tools where you have added an API token are handled through their member API; the rest by an agent in your own Chrome, in tabs where you are already signed in as an admin. Any step that would add a paid seat stops and waits for your approval, and every change lands in an audit log, which is the first-week record done for you.

It does not touch devices, passwords or two-step verification, and it is not SSO: people still sign in to each tool the way they do now. The agent needs your Chrome open to run, and it can fail when a tool redesigns its admin pages (a failed run says so and shows its last screenshot). It costs a flat fee from $199 a month, billed annually, however many people and tools you have (pricing). How it works shows the flow.

FAQ

What does IT need for a new hire?
IT needs the start date, role, team, manager and contract type as soon as the offer is signed. With those, it can prepare the laptop, create the main account, and invite the person to the tools their role needs, with the right role inside each tool.
How early should accounts be set up?
Create the main Google Workspace or Microsoft 365 account and send tool invites two to five days before the start date. Earlier, invites can expire or the offer can fall through; later, the first day is spent waiting for emails.
Should new hires get admin rights?
No. New hires should get a standard user account on their laptop and the plain member role in each tool. Admin rights are granted later, for a specific reason, and recorded.
How do I give access by role?
Write down, for each job, which tools it gets and which role inside each tool. When someone new joins in that role, you work down the list instead of deciding from memory, and the same list tells you what to change when they move or leave.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google