The JML process (joiners, movers, leavers) is how a company handles every change to a person's access: what they get when they join, what changes when they move to a new role or team, and what is removed when they leave. Joiners and leavers get attention because they are obvious events. Movers are the quiet middle, and that is where most excess access comes from.
A 20-person company does not need an identity governance platform to run JML. It needs one owner, a written list of what each role gets, and a record of every change. This post sets that up.
What JML means
The term comes from larger organizations' IT and audit work, where "joiner-mover-leaver" is the standard way to describe the access lifecycle. A joiner is someone who starts: you create their accounts and give the access their role needs. A mover is someone whose job changes while they stay, whether that is a new team, a promotion, a new manager, or a switch from contractor to employee: you add what the new role needs, and remove what the old role needed and the new one does not. A leaver is someone who goes: you remove all access, recover devices and data, and free the seats.
Every access change you will ever make fits one of the three. That is the point of the model: if you have a process for each, you have a process for everything. User lifecycle management looks at the same ground from the account's side, through the states an account passes through between these events.
Joiners
Joiners are the easiest of the three, because everyone wants them to go well. The new hire wants their logins, the manager wants them productive, and the person doing the invites has a start date to work towards. Four things make joiners repeatable.
A trigger. The signed offer, logged somewhere the person doing the invites will see it. Not a hallway mention.
A role bundle. A written list of the tools and the role inside each tool for that job. Without it, every joiner is decided from scratch. Role-based access control shows how to write one.
Approval for paid seats, by a named person.
A record of what was given, with the date.
The employee onboarding checklist and the IT onboarding checklist go through the joiner steps in detail. The only JML-specific point is the last one: the record you make at the joiner stage is what makes the mover and leaver stages possible.
Movers: the forgotten middle
A mover is anyone whose access needs should change while they stay at the company. In a small company that happens constantly, often without anyone calling it a move. A support agent moves into customer success. An engineer becomes the engineering manager. A salesperson takes over a region, or hands one off. A contractor becomes an employee, or an employee drops to part-time contracting. Someone covers for a colleague on leave for three months. A founder hands finance to a new operations hire.
Each of these should trigger an access change. Usually only half of it happens. The person gets what the new role needs, because they ask for it. Nobody removes what the old role needed, because nobody asks for that. Over a few moves, the person accumulates access to everything they have ever touched. The security term is privilege creep, and it is why the people who have been around longest usually have the most access. The principle of least privilege is the rule privilege creep breaks.
Why it matters: every account is a door. Someone who moved out of finance two years ago does not need the bank portal, and if their laptop or password is ever compromised, it is one more thing exposed. It also costs money, in seats nobody uses, and it makes the eventual leaver stage harder, because their access no longer matches any role.
How to run a move
Treat a move as two operations, not one: an addition now and a removal later.
Compare old and new. Take the old role's bundle and the new role's bundle. The difference is the change: tools to add, tools to remove, and tools where the role inside changes (member to admin, editor to viewer).
Add what the new role needs on the day the move starts.
Set an end date for the old access. Most movers need a handover period, so removing everything on day one breaks real work. Agree a date, usually a few weeks out, and put it in a calendar with someone's name on it.
Remove the old access on that date. This is the step that gets skipped. Make it a task with an owner, not an intention.
Check for access outside the bundle. People pick up tools and roles that were never in any bundle: the analytics tool from one project, admin rights granted to fix one problem. A move is the right moment to look at what they actually have, not just what their role says they should have.
Record both sides. What was added, what was removed, when, and who approved it.
A worked example
Say Sam moves from support to customer success. The support bundle had the help desk as an agent, the support channels in Slack, and view-only access to the CRM. The customer success bundle has the CRM with a full seat, the customer success channels, and the help desk as a viewer, so Sam can still read ticket history.
The move is then three changes, not a rebuild. On day one, Sam gets the full CRM seat (a paid seat, so it waits for approval) and the new channels. Two weeks later, after handing over open tickets, Sam drops from agent to viewer in the help desk and leaves the support channels. Whether that downgrade also frees a paid seat depends on how your help desk bills viewers, so check before you count the saving. And the move check finds the one thing no bundle listed: Sam was made admin of the help desk last spring to set up a macro. That goes too.
Moves that need extra care
Promotions to manager often come with approval powers: expenses, hiring tools, payroll views. Grant those on purpose, not by copying the previous manager's settings.
Temporary cover should always have an end date from the start, because "temporary" access that is never removed is just access.
Contractor to employee, and back. A contractor who joins the staff often keeps their old guest or external account next to the new one. Merge or remove it. An employee who drops to contracting should lose everything a contractor would not get, on the day the contract changes.
Leavers
Leavers get attention because the risk is easy to picture. The work is: remove access everywhere on the last day, recover devices, move their data, cancel their seats, and check a week later for anything missed.
Freeing seats is easy to forget in the main account itself. Google's help page on suspending users, as we read it on 27 October 2026, says plainly that "Suspended accounts are still charged" at the same rate as active ones, and suggests deleting an account you no longer need (source). So suspension is the right first step, because it blocks sign-in and keeps the data, but it is not the last one. Transfer the files, then delete or reassign the license. Google Workspace offboarding has those steps in order.
The one dependency is the same as for movers: you can only remove access you know about. If the joiner and mover stages were recorded, the leaver stage is a list. If they were not, it is an investigation. The employee offboarding checklist has the full steps, and the offboarding process covers who does what.
One record for all three
What ties JML together is a single record of who has access to what, with what role. Joiners write to it, movers change it, leavers empty it. A spreadsheet works if someone keeps it current; a tool that reads the access from the tools themselves is better, because it cannot drift from reality.
Who owns JML in a small company
Three roles, which may be the same person. The trigger is whoever knows about the change first: usually HR or the founder for joiners and leavers, and the manager for movers. Their job is to tell the owner, in one fixed place. The owner is whoever runs IT and operations. They make the changes, or make sure they are made, and keep the record. The approver is the person's manager, for anything beyond the bundle and for paid seats.
Movers fail most often at the trigger. Nobody files a ticket for "Sam now does customer success". Make it a habit that any change of title, team or manager is announced to the owner, the same way a new hire is. If your HR tool or Google Workspace profile holds job title and manager, a change in those fields is a mover event, and checking for such changes once a month catches the ones nobody announced.
Documenting JML for an audit
If you face a security questionnaire or an audit such as SOC 2, expect to be asked how access is granted, changed and removed, and to show evidence. What counts as enough is your auditor's call, but evidence usually covers five things. First, a short written process for each of the three stages; an access control policy is the usual home for it. Second, the role bundles, so "appropriate access" has a definition. Third, for a sample of joiners, movers and leavers, the date of the change, the request, the approval, and what was done. Fourth, proof that leavers lost access promptly, compared with their last day. And fifth, regular user access reviews, which catch what the process missed.
Healthcare companies have the same expectation in regulation. The HIPAA Security Rule lists "Termination procedures" for ending access to electronic protected health information, and procedures to "establish, document, review, and modify a user's right of access", both as addressable implementation specifications in 45 CFR 164.308, as we read it on 27 October 2026. That is leavers and movers, in regulatory language.
Most small companies can produce the joiner and leaver evidence. The mover evidence is usually what is missing.
Where to start this week
Pick the two roles you hire most and write their bundles. Then list everyone who changed title, team or manager in the last year, and compare what each of them has with their current bundle. That one comparison usually finds more excess access than anything else you could do in an afternoon, and it shows you whether your mover step exists at all.
Where SmashSSO fits
SmashSSO keeps the single record and runs all three stages from it. It reads your people from Google Workspace and shows, for each tool, who has an account and with what role. Joiners get an access bundle; a mover gets the new bundle, and the role changes and removals run the same way as the invites. When someone is suspended in Google Workspace, it alerts you and shows where they still have access. Paid seats pause for approval, and every change is written to an audit log, which is the mover evidence most companies lack.
Changes go through a tool's member API where you have added a token, and otherwise through an agent in your own Chrome, which has to be open to run. It needs Google Workspace as the directory, it has no SOC 2 report of its own, and it is not SSO. It costs a flat fee from $199 a month billed annually (pricing). The user provisioning hub has the rest of this cluster.