How to Automate Employee Access Onboarding and Offboarding

When someone new joins a business, someone has to give them access to email, the sales system, the team's WhatsApp group, the shared folder, the point of sale, the CRM, and the two or three tools used daily. That process is almost never written down. It happens by hand, from memory, spread across several people, and the result is that the new hire spends their first three days asking for access that someone forgot to set up.

The other side is worse and almost nobody checks it. When someone leaves, they get their access revoked for whatever people remember in the moment: usually email and little else. Months later, that former employee is still in the WhatsApp group where orders get coordinated, still has permissions on the pricing folder, and their user account is still active in the system. Nobody did it out of bad intent: nobody was simply keeping a list of what access they had.

Why this process goes wrong almost everywhere

The reason is that access onboarding and offboarding doesn't belong to anyone. HR handles the contract, the direct manager handles training, and whoever knows systems handles access, but that third person often doesn't find out about the hire until the new person has already arrived, or about the departure until days later. The process lives in the gaps between departments, which is why it's always incomplete.

The second reason is that the list of tools grows without anyone updating it. A business that used two systems five years ago now uses nine, between email, messaging, point of sale, invoicing, the cloud where files live, and vendor platforms. Nobody ever wrote down that full list, so onboarding happens from memory, and memory fails exactly on the tools that get used the least, which tend to be the ones holding the most sensitive information.

What part of this process can be automated

• Automatically trigger the full list of access that corresponds to a role as soon as a hire is registered.
• Assign each task to whoever executes it, with a deadline, so no access is left pending in limbo.
• Give the new employee a checklist of what they already have and what's missing, instead of having them ask around.
• Run a complete offboarding on the day someone leaves, covering every system on the list and not just the ones someone remembers.
• Keep a record of what access was granted and revoked, with dates, which is what you need in an audit or when there is a problem.
• Periodically review which active users no longer correspond to anyone who works at the business.

What makes this automatable is that it doesn't require judgment: a given role always needs the same access. When the process lives in a custom-built system for the business, hiring someone triggers the list on its own, each task reaches the right person, and offboarding runs in full without depending on anyone remembering. What today takes three days of back and forth becomes something that's already done by the time the person arrives.

The risk isn't the access you forgot to grant. It's the one you forgot to revoke.

What changes when the process is organized

The first thing is that a new employee's first day stops being a wasted day. In many businesses, the person coming in spends their first week at half capacity because they're missing tools. Multiplied across every hire of the year, that's a significant amount of salary paid for time that couldn't be productive, and it's entirely avoidable.

The second is that it closes off a real risk. A former employee with access to the client list, purchase prices, or the group where operations get coordinated is an exposure most owners don't know they have open. It doesn't take bad faith for that to end badly; it's enough for that person to go work for a competitor.

The third is that a list appears that did not exist before: which tools the business actually uses and who uses them. That list almost always reveals subscriptions still being paid for users who are long gone and duplicate systems doing the same thing. Organizing the access process usually pays for itself with what you stop overpaying.

Where to start

Start by making the list that doesn't exist: sit down for an hour and write down every tool, system, group and account your business uses. Then, for each role, mark which ones apply. With just that, you've already done eighty percent of the work, because the problem was never executing the onboarding, it was knowing what needed to be set up. The next step is to check who has access today and compare it against who actually works with you today. That review, in most businesses doing it for the first time, turns up at least two or three users who shouldn't still be there.