Skip to content

Blog

User lifecycle management

User lifecycle management covers every account from creation to deletion. The states, the tools, and how small teams run it on Google Workspace.

· 8 min read

User lifecycle management is the practice of managing a person's accounts and access from the moment they are first created to the moment the last one is removed: creation, changes along the way, suspension, and deletion. "Identity lifecycle management" is the same thing under the name identity vendors prefer. For a small company it comes down to two questions you should always be able to answer: who has access to what right now, and how does that change when something happens to a person.

Enterprise IAM (identity and access management) suites sell this as a platform. A small team can do most of it with a directory it already has, a written set of roles, and a habit of checking.

The lifecycle

The usual diagram has three boxes: join, move, leave. That is the JML process, and it covers the events. The lifecycle is the states a user account passes through between those events, and there are more of them than three:

StateWhat it meansWhat should be true
Pre-startAccount created before day oneExists, but nothing sensitive yet; invites sent to work email only
ActiveWorking normallyAccess matches their role, and nothing more
ChangedNew role, team or managerNew access added, old access removed by a set date
On leaveParental leave, sabbatical, long sick leaveAdmin rights and sensitive access paused; ordinary access usually kept
SuspendedDeparted, or blocked during an investigationCannot sign in anywhere; data kept; seats freed where possible
DeletedGone for goodData transferred or retained as your policy says; account removed

Two of these are routinely skipped. On leave gets no thought at all, so either someone's admin access sits unused for months, or their account is suspended and they come back to a pile of broken invites. Decide the rule once. A workable default: keep ordinary access so they can return without friction, hand their admin roles to the backup admin for the duration, and write the return date next to both.

Deleted gets rushed: someone deletes the main account to free a license before moving the person's files, and the files go with it. The opposite mistake is just as common. Accounts sit in Suspended forever, and in Google Workspace that costs money: Google's help page on suspending users says "Suspended accounts are still charged" at the same rate as active accounts, as we read it on 27 October 2026 (source). Suspension is a waiting room, not a destination. Transfer the data, then delete.

Accounts that are not people

Not every account belongs to a person who joins and leaves. Shared logins, service accounts for integrations, bots and API tokens all have lifecycles, and nobody's last day triggers their removal. Give each one a named owner, and treat the owner's departure as that account's leaver event. Shared accounts and orphaned accounts cover what goes wrong when you do not.

Identity lifecycle management, and the tools that claim it

Search for identity lifecycle management and you will find the same idea framed around the identity rather than the account: one person, one identity in the directory, and many accounts hanging off it. The framing is useful because it puts the directory at the center. In practice, five kinds of software claim this job, and they overlap less than their marketing suggests.

The HR system knows employment facts: start date, title, manager, last day. It is often the true start of the lifecycle, but most small-company HR tools do not create accounts in your other tools.

The directory or identity provider (Google Workspace, Microsoft Entra ID, Okta, JumpCloud) holds the main account and groups. With SCIM (a standard API for pushing account changes), it can create and remove accounts in connected tools, if those tools' plans support it. What is SCIM covers that, and the price of the plans it lives on.

Identity governance (IGA) platforms add approvals, access requests and certification campaigns on top. They are built for large companies with compliance teams, and priced that way.

SaaS management tools discover which tools you use and who is in them, often with spend tracking. Some can make changes, some only report.

A spreadsheet maintained by hand. Free, and accurate exactly as long as someone keeps it current.

Do you need a dedicated tool? Not to start. You need the directory you already have, written roles, and a record of changes. A tool earns its place when the record keeps drifting from reality, which in practice happens somewhere past the point where one person can remember every tool. At five people, that point may never come. At thirty, with a new tool adopted every month, it usually has. Identity and access management for small businesses puts these categories in the wider IAM picture, and IAM tools compares specific products.

Directory as source of truth

Pick one place that says who works here, and make everything else follow it. For most small companies on Google Workspace, that is Google Workspace. Four things make a directory a good source of truth.

Every person is in it, including contractors who need tool access. Someone with access to your tools who is not in the directory is invisible to every process you build. If you do not want to pay for a full Workspace license per contractor, decide where they are recorded instead, and make that list part of the same reviews.

Group membership reflects role. An "engineering" group, a "sales" group. Groups are how a directory says what someone does, and many tools can read them.

Profile fields are filled in. Google Workspace user profiles have fields for things like job title, department and manager. Keep them current and a change in them becomes a signal that someone has moved.

Status is honest. When someone leaves, suspend them in the directory first. Suspension blocks sign-in and keeps their data, so you can transfer files before anything is deleted. Google Workspace offboarding has the steps.

The directory being right is necessary but not enough. Suspending someone in Google Workspace stops them signing in to Google, and to tools they reach through "Sign in with Google". It does not remove their account in tools with their own passwords, and it does not end sessions already open there.

Tool-side changes

This is where lifecycle management usually breaks. The directory changes; the tools do not follow.

Each tool keeps its own list of members, with its own roles. Unless something connects them, the directory and the tools drift apart in three ways. There are people in tools who are not in the directory: old contractors, personal email addresses, the test account someone made. These are orphaned accounts. There are people in the directory with the wrong access in tools, such as a mover who kept their old team's admin role. And there are people who left the directory but not the tools: suspended in Google, still a member of the design tool, still holding a paid seat.

There are three ways to close the gap. SCIM, where your plans include it. Scripts or workflows against each tool's member API, where someone will maintain them. Or a process that compares the directory with each tool's member list and makes the changes, by hand or with software. Whatever you choose, the comparison needs to happen on every lifecycle event, not just when someone remembers. Provisioning and deprovisioning looks at designing both ends together, and the hub on user provisioning covers the joiner end in depth.

Reviews

Processes miss things. A periodic review catches what they missed.

A user access review means going through each important tool's member list, checking each account against the directory and the person's role, and fixing what is wrong. Quarterly is a common rhythm for small teams; what matters more is that it happens on a schedule and leaves a record. The user access review post has a process and a template.

Look for the three drift patterns above, and then four more. Who holds admin roles, and does each one still need them? Which paid seats belong to people who have not signed in for months? Which accounts sit on personal email addresses? And which service accounts and tokens have no living owner?

Each finding is also feedback on the process. If the review keeps finding movers with old access, the mover step is broken, not the review.

Common mistakes

Most lifecycle failures are not exotic. Inviting someone to tools before their work email exists, so their first account is on a personal address. Treating the directory change as the whole job, so suspension in Google is assumed to mean removal everywhere. Deleting before transferring data. Leaving accounts suspended indefinitely and paying for them. And giving non-human accounts no owner, so they outlive everyone who knew why they existed.

If you fix one thing this month, make it the link between the directory and the tools: every time someone's status changes in Google Workspace, someone checks every tool they are in. The rest of the lifecycle gets easier once that is reliable.

Where SmashSSO fits

SmashSSO does the tool-side part of user lifecycle management for companies on Google Workspace. It reads your directory with read-only access and builds an access grid: for each tool, who has an account and with what role, matched by email. Accounts that match nobody in the directory are flagged. Access bundles by role handle joiners; role changes and removals run the same way. When someone is suspended in Google Workspace, it alerts you and shows every tool they are still in.

Changes run through a tool's member API where you have added a token, or an agent in your own Chrome where you have not; the agent needs that browser open and can fail when a tool changes its screens. Every change is recorded in an audit log. It does no spend tracking and has no CSV export, and it is not SSO. It costs a flat fee from $199 a month billed annually (pricing).

FAQ

What is user lifecycle management?
User lifecycle management is managing a person's accounts and access from the first account created to the last one removed. It covers creation, changes when their role changes, suspension when they leave, and deletion.
What is identity lifecycle management?
Identity lifecycle management is the same practice under the name identity vendors prefer. It frames the job around one identity in the directory, with the accounts in every tool following that identity's changes.
Do I need a tool for it?
Not to start. A directory you already have, written roles and a record of changes are enough for a small team. A dedicated tool earns its place when the record keeps drifting from what the tools actually contain.
How does Google Workspace fit in?
For most small companies, Google Workspace is the source of truth for who works there, through its users, groups and profile fields. Suspending someone there blocks their Google sign-in, but it does not remove their accounts in tools with their own passwords, and suspended accounts are still billed.

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