Skip to content

Blog

Employee onboarding checklist: the accounts part

An employee onboarding checklist for small companies: before day one, day one and week one, with the accounts step that most checklists skip done properly.

· 9 min read

A complete employee onboarding checklist runs in three stages: before day one (contract, payroll, equipment, accounts, a welcome note), day one (a working laptop, every login working, introductions, the first conversation with their manager) and the first week (training, a first real piece of work, and a check-in). The full checklist is near the bottom, one short paragraph per step. This post goes deepest on the line most checklists skip: the accounts.

Here is the whole onboarding process at a glance, for a small company:

WhenPeople and paperworkAccounts and equipment
Before day oneSigned contract, payroll and tax details, a welcome email with the first-day planLaptop ordered, work email created, tools invited by role, paid seats approved
Day oneWelcome from the manager, introductions, a buddy, the handbook and key policiesLaptop signed in, two-step verification on, every invite accepted
First weekTraining, a first small task, a short check-in with the manager on day fiveMissing access fixed, unneeded access removed, what they have recorded

Everything in the left column belongs to HR or the manager, and plenty of good guides cover it. The right column is where a new hire actually loses their first morning.

Where onboarding checklists fall short

Most onboarding checklists treat accounts as one line: "Set up accounts and tools". That line hides a dozen separate jobs, each in a different admin page, each with its own choices.

Which tools? Which role in each? Which Slack channels, which GitHub teams, which shared drives? Does the new seat cost money, and who said yes to it? Who checks that the invite to the analytics tool was accepted and not lost in spam?

Because the line is vague, the work is done from memory, and memory is uneven. The second engineer you hire gets everything the first one had asked for over months. The fifth gets whatever the person doing the invites remembers that morning. Nobody writes down what was given, so when the person leaves, nobody knows what to remove.

What employee onboarding software does, and does not

Employee onboarding software (a standalone tool, or the onboarding module of your HR platform) helps with the left column: e-signatures, forms, task lists, welcome pages. It can assign a task called "Create Slack account" to someone. It usually does not create the account. Check before you assume it does, and ask the vendor which tools it can actually add people to, with which role. A task list that tells someone to do fifteen invites is still fifteen invites.

Accounts and tools by role

Split the accounts into three groups, and give each group an owner. That is what turns one vague line into a list that actually gets done.

Everyone gets these. Work email and calendar, chat, video calls, the password manager, the HR and payroll portal, the company wiki. Owned by whoever runs IT, even if that is a founder.

The role decides these. Engineers get the code host, issue tracker, hosting and error monitoring. Designers get the design tool. Sales gets the CRM and the call recorder. Support gets the help desk. Owned by IT, with the team lead saying what "Engineer" means.

The team grants these. Specific Slack channels, the GitHub team for their squad, the customer folders for their accounts, the finance tools only the finance person touches. Owned by the manager, because only the manager knows.

For each account, record the role inside the tool as well as the account itself. A member and an admin in the same tool are very different things to give someone on day one. Role-based access control goes through how to define those roles once for a small company.

Order of operations

The order matters more than people expect. Do it in this sequence and most first-day failures disappear.

Start with the main account in Google Workspace or Microsoft 365, because almost every other tool is invited by work email or signed in to with it. Then add the person to the right groups. Group membership often grants shared drives, calendars and mailing lists at once, and doing it before the tool invites means the tools that read groups will see them.

Next come the free and baseline tools: chat, video calls, the wiki. These rarely cost extra per person and are needed on day one. Role tools follow, after approval, since anything that adds a paid seat waits for a yes (more on that below). Sensitive access comes last, and on purpose. Production systems, billing and admin roles are granted when the work needs them, not as part of the welcome pack.

Send invites two to five days before the start date. Earlier, and invites expire or the offer falls through; later, and day one is spent waiting. If someone's start date moves, move the invites with it.

Many tools bill per seat, and in many of them a seat is added the moment someone joins. Invite a new hire to the design tool "just in case" and you may be paying for a full seat they open twice. Three habits keep this under control.

Name an approver for paid seats. Usually the manager for their own team's tools, and the founder or finance for anything expensive. Approval can be a one-word reply in a thread; what matters is that it exists.

Prefer the cheapest seat that does the job. Several tools sell different seat types. Figma, for example, lists Full, Dev and Collab seats at different prices on its pricing page as we read it on 27 October 2026. A product manager who comments on designs does not need the seat a designer needs.

Watch domain auto-join. Tools that let anyone with your email domain join are convenient, and every person who wanders in may be a seat on the next invoice. Check which of your tools allow it.

Contractors deserve a separate look, because their seats are where money leaks quietly. In Slack, multi-channel guests are "billed as regular members", while single-channel guests are free, up to five per paid active member, per Slack's guest help article as we read it on 27 October 2026. A freelancer who only needs one project channel can be a free guest instead of a paid member. SaaS license management covers the other half of the problem: finding the seats you already pay for and do not use.

Bundles for repeat roles

An access bundle is a named list of tools and roles for one kind of job: "Engineer", "Account executive", "Support agent". It is the single biggest improvement you can make to onboarding, and it costs nothing to start.

Write one for every role you have hired twice. A bundle has three columns: the tool, the role inside it, and whether it is a paid seat. When the next person in that role joins, you do not decide anything. You work down the list.

Bundles help at the other end too. When someone changes team, compare their old bundle with the new one and change only the difference. When someone leaves, the bundle tells you where to look first, though not everywhere: people collect access outside their bundle, which is why the first-week record matters. User provisioning, the hub for this topic, shows a sample set of bundles, and how to automate onboarding covers the ways to run one without doing each invite by hand.

How long onboarding takes

The accounts part takes about a week of calendar time and a few hours of work: invites a few days before the start, setup on day one, a check on day five. The wider onboarding process, until someone is fully productive, takes much longer and depends on the job; nobody can give you an honest single number for it.

What you can control is how much of the first week is spent waiting. A new hire who spends Monday chasing invites has lost a day that no welcome lunch gets back. The goal for the account side is simple: by noon on day one, everything in their bundle works.

Edge cases worth deciding in advance

Rehires. Someone coming back may still have accounts from last time, sometimes with their old role. Search before you invite, and do not reactivate an old admin account for a new member job.

Interns and short contracts. Give them an end date at the start, in every tool that supports one, and in your own record for those that do not. Contractor access management covers the rest of the contractor case, from guest accounts to the day the engagement ends.

Two people starting the same day. Run them through the same bundle, in the same order. Differences between their access should be explainable by their roles, not by who did the invites.

Someone who starts remote. Ship the laptop early enough for a delay, and do the first password handover on a video call.

The checklist

Copy this into your HR tool, a doc or a ticket. Each step names its owner, so nothing falls between HR and IT.

Before day one

Sign the contract and collect payroll details. Tax and bank details too. Owner: HR or the founder.

Name the manager and a buddy, and write the first-week plan. Owner: the manager.

Order or prepare the laptop, encrypted and updated. Owner: IT.

Create the work email and add it to the right groups. Owner: IT.

Invite the baseline tools: chat, video calls, wiki, password manager, HR portal. Owner: IT.

Choose the role bundle and get paid seats approved by the named approver. Owner: IT, with the manager.

Invite the role tools, with the role set inside each. Owner: IT.

Add team channels, drives and projects. Owner: the manager.

Send the welcome email with the first-day plan and how the first password will arrive. Owner: HR or the manager.

Day one

Welcome and introductions, with the handbook and key policies shared. Owner: the manager.

Sign in to the laptop, change the password, and turn on two-step verification. Owner: IT, with the new hire.

Confirm every invite was accepted and works. Owner: IT.

Hold the first conversation with the manager about the role and the first month. Owner: the manager.

First week

Start training and a first small task. Owner: the manager.

Fix missing access and remove access they do not need. Owner: IT.

Record each tool and role, with the date. Owner: IT. This is what makes their offboarding a list rather than an investigation.

Hold the day-five check-in. Owner: the manager.

The IT onboarding checklist has the device and security steps in more detail, for whoever sets up the laptop.

Where SmashSSO fits

SmashSSO is built around the right-hand column. It reads your people from Google Workspace and shows, in one grid, who has an account in each tool and with what role, matched by email. You write your bundles once as access bundles; assigning "Engineer" to a new hire invites them to every tool in it with the right role. A step that would add a paid seat pauses until someone approves it, and every change goes into an audit log, so the "record each tool and role" step takes care of itself.

Where you have added a tool's API token, it works through the tool's member API. Elsewhere an agent does the invite in your own Chrome, in tabs where you are already signed in as an admin; that browser has to be open, and agent runs are slower than an API. It is not SSO, and it does not do the paperwork, the laptop or the welcome lunch. It costs a flat fee from $199 a month billed annually (pricing).

FAQ

What should be on an onboarding checklist?
A good onboarding checklist covers the paperwork, the equipment, the accounts and the first week of work. For accounts, it should name the tools and the role inside each one, who approves paid seats, and a check on day five that everything works and nothing extra was given.
How do I set up accounts for a new employee?
Create the work email first and add it to the right groups, then invite the baseline tools everyone gets, then the role's tools once any paid seats are approved. Leave sensitive access such as production or billing until the work needs it.
What is an access bundle?
An access bundle is a named list of tools and the role inside each one for a kind of job, such as Engineer or Support agent. When someone joins in that role, you give them the bundle instead of deciding each tool again.
How long does onboarding take?
The accounts part takes about a week of calendar time: invites a few days before the start, setup on day one, and a check on day five. Becoming fully productive takes much longer and depends on the job.

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