ExploreWhat I doWebsitesAppsAutomations and AIReady-made business toolsLooking after it afterwardsProblems I fixMy workHow it worksFree website checkAboutAbout meCommon questionsGet startedRequest a free chatClient login
All projects

Staff onboarding and account removal

Setting someone up meant remembering dozens of steps across six systems, and people who left could keep their access. Now it runs in order and checks itself afterwards.

Built and run for a real business, in my previous roleReal workflows, names blurred

Onboarding workflow, replayed as a live run.
Each replay shows the real workflow lighting up step by step, the way it looks while it runs.Names of people, suppliers and products are blurred.
In shortAbout three hours of somebody’s time back on every new starter and every leaver.Both paths were tested from start to finish on test accounts made for the job. Afterwards I checked inside every system that each change had really happened. A step that fails stays on the screen instead of being counted as done.

What was going wrong

Setting up a new employee meant manual steps across accounts, licences, groups, mailbox, phone and device. Someone who left could keep their access, because the checklist lived in one person’s head.

Why it mattered

New staff sat waiting for things they needed on day one. Worse, access that should have been switched off stayed on, and there was no dependable record of what had been created, changed or removed.

What it changed

About three hours of somebody’s time back on every new starter and every leaver. That was the setting up and the shutting off, done by hand across six systems. The bigger change is that a missed step now shows up the same day instead of turning up weeks later as access that should have been switched off.

Built with

Workflow automationMicrosoft 365Six systems, one triggerA record of every step

How it works

When someone joins the business, this sets up everything they need for day one, in the right order. When someone leaves, it shuts off their access properly. Both write down exactly what they did.

The main screens

Onboarding workflow, replayed as a live run.
Onboarding workflowThe steps that run for a new starter, replayed the way they look while a real run is going. Each step lights up as it finishes.
Onboarding run, replayed as a live run.
Onboarding runA real finished run of an earlier version, played back from the start.
Offboarding workflow, replayed as a live run.
Offboarding workflowThe steps that run for a leaver, from waiting until their last day to sending the report.
Offboarding, second business, replayed as a live run.
Offboarding, second businessThe same leaver process built for a second business, which uses a few different systems.

Everyday jobs

Set up a new starter

  1. Form: A manager fills in the new starter form. Once it is approved, every step below runs on its own, in order.
  2. Tidy up: It tidies up the person's name and saves a PDF copy of the form.
  3. Account: It checks whether they already have a work account in the email and identity platform. It uses that one, or makes a new one. If that fails, IT is told straight away.
  4. Licence: It sets their location, counts the spare licences (the paid right to use the software) and gives them one. If none are spare, it asks the IT provider to buy one.
  5. Access: It adds them to the right security groups and email lists, and opens up the shared file folders their role needs.
  6. Phone: It makes their softphone extension, waits for the phone system to catch up, fills in their profile and puts them in the right call queues.
  7. Other systems: It sets up or asks for every other system ticked on the form: a CRM seat (the customer system), an ERP login (the accounting and stock system), design software, their email signature and any industry software.
  8. Report: It waits for every branch to finish, then emails one report with the form attached. Anything only a person can do is listed at the top.

Shut off a leaver

  1. Fill in the leaver form, including their last working day.
  2. 5pm, last day The system waits until 5pm on that day, so they keep access for their whole last day.
  3. It blocks their sign-in, signs them out on every device and clears their email signature details.
  4. It takes them out of every security group and email list.
  5. It turns on an automatic reply if one was asked for. It can keep the mailbox as a shared mailbox for their manager, then it frees up the licence.
  6. It removes their softphone extension and their shared file access.
  7. It removes them from the email marketing list and checks it worked. It also removes them from the CRM, the ERP, design software, the meeting tool and any industry software, or asks the right person to.
  8. It puts every result into one report, attaches the leaver form and emails it to the person who asked.

Read the report

  1. Open the report email that arrives when the run finishes.
  2. Check each step's result. A failed step stays marked as failed, never counted as done.
  3. Look at Do these by hand for anything only a person can do, such as an office key fob.
  4. Check who each request went to, and when to chase it.

Still done by a person

  • Anything only a person can do, such as an office key fob, is listed at the top of the report.
  • If no licence is spare, it asks the IT provider to buy one.

Who can see what: Every run starts from a form a person has approved. Anything that costs money goes to a person as a request, and every step is written down, so there is always a record.

The technical detail

  • 75+steps in the joiner process
  • 55+steps in the leaver process

What I built

A joiner process of more than 75 steps and a leaver process of more than 55 steps, both live. Each one checks what it is given, takes a different path where it has to, sends the right people a message, deals with a step that fails, and writes down the result.

How it works

An approved form supplies the new person’s details. The steps then run in order: accounts, licences, groups, mail, files, phone and the customer system (a CRM). The leaver process runs at 5pm on the last day. Anything only a person can do is written into the report.

Where it got to

Both paths were tested with throwaway accounts, and the result was read back out of Microsoft 365, Exchange, SharePoint, the phone system and the customer system (a CRM). A run that fails stays on the screen rather than being counted as a success.

Please note: these are the real workflows. Names of people, suppliers and products are blurred, and no personal details appear in them.

Still setting people up by hand?

Tell me where the work gets stuck. You will get a straight answer on what to do next.

Request a free chat