Skip to content

Blog

Identity and access management for small businesses

Identity and access management for small businesses: directory, login, access and review, what each costs, and the process that matters more than the tool.

· 14 min read

Identity and access management (IAM) is how a company keeps track of who its people are, decides what each of them can reach, and changes that quickly when someone joins, moves or leaves. For a business of 5 to 50 people, it comes down to four things: one list of people, one way to log in, a record of who has access to which tool, and a habit of checking that record.

Enterprise IAM is a market of large platforms with long feature lists. Small-business IAM is mostly a process with a few tools around it. This guide covers both, so you can tell which parts of the pitch apply to you, what each piece costs, and what to do first.

What IAM means

The term joins two jobs that are worth keeping apart.

Identity management answers "who is this?" It covers the list of people in your company, their accounts, and how they prove they are who they say: passwords, MFA (multi-factor authentication, a second check such as an app prompt or security key), and single sign-on.

Access management answers "what can they reach, and should they?" It covers which tools each person has an account in, what role they hold there (member, admin, owner), and how that changes over time.

The words you will meet, in plain terms:

TermWhat it means
DirectoryThe master list of your people. Google Workspace or Microsoft 365 for most small companies.
AuthenticationProving who you are: password, MFA, SSO.
AuthorizationWhat you are allowed to do once you are in: your role in each tool.
Identity provider (IdP)The service that checks logins and vouches for people to other tools (explained).
SSOSingle sign-on: one login accepted by many tools (what SSO is).
ProvisioningCreating accounts and giving access (user provisioning).
DeprovisioningRemoving accounts and access when someone leaves or changes role (deprovisioning).
SCIMA standard API identity providers use to create and remove accounts in tools automatically (what SCIM is).
RBACRole-based access control: access decided by job role, not person by person (RBAC).
Least privilegeGive each person the access their job needs and no more (least privilege).
Access reviewPeriodically checking that everyone's access is still right (user access review).
JMLJoiners, movers, leavers: the three moments access has to change (JML process).

A large company buys separate products for many of these rows. A small one needs every row covered, by something, without hiring an identity team.

Access management: the half that gets skipped

Most IAM marketing is about identity: logins, MFA, SSO. That is the half your directory already handles reasonably well. The weak half in a small company is access management, because no single system holds the answer to "who can get into what".

Access management covers three questions. Which accounts exist in each tool, and does each one belong to someone who still works here? What can each account do: is that contractor a viewer or an admin? And who decided, and when? An identity provider answers none of these for a tool it is not connected to, and even for connected tools it usually knows only who may log in, not what role they hold once inside.

That gap is why a company can have perfect MFA and still find a former employee with admin rights in the billing tool. The login was secured. The access was never managed.

The parts: directory, login, access, review

Every IAM setup, from five people to fifty thousand, has the same four parts.

The directory

One authoritative list of who works for you. Everything else hangs off it. For most small companies the directory already exists: it is Google Workspace or Microsoft 365, because that is where everyone's email lives. The rule that matters: nobody gets access to anything without being in the directory first, and leaving the company starts with being suspended there.

Contractors are the usual hole. If they do not get a company account, they are not in the directory, and their access to your tools is tracked nowhere (contractor access management covers how to fix that).

Login

How people prove who they are to each tool. There are three levels, in order of strength and cost. The weakest is each tool's own password, ideally from a password manager and with MFA switched on in the tool. Next is "Sign in with Google" or Microsoft where a tool offers it on your plan: one account, its MFA applies, and it is often free. Strongest is enforced SSO through an identity provider, where the tool refuses any other login; it usually sits on the tool's most expensive plan. SSO vs MFA explains why MFA comes before SSO, and SSO vs a password manager covers the tools that will never support SSO.

Access

Which accounts exist, in which tools, with which role. This is where small companies are weakest, because no single system knows the answer. Google knows who your people are; each tool knows who has an account in it; nothing joins the two unless you do.

Access has three moments: when someone joins (create the accounts their role needs), moves (change roles, add some tools, remove others), and leaves (remove everything, on the day).

Review

Periodically checking that what is true matches what should be true. Who still has admin rights? Which accounts belong to nobody in the directory? Which paid seats belong to people who left in spring? A short quarterly review catches what the other three parts missed. When a customer or auditor wants proof that reviews happened, that is called access certification.

What a small business actually needs

Most IAM features are built for problems you do not have yet. Here is what is worth doing at 5 to 50 people, roughly in order.

One directory, used for everyone, contractors included where possible.

MFA enforced on the directory account. In Google Workspace that is 2-Step Verification, enforced from the admin console; Google's deployment guide, as we read it on 27 October 2026, lets you require any method, any method except text and phone codes, or only security keys and passkeys. This is the single most valuable control on the list, because the directory account is the key to everything else. Our Google Workspace security checklist covers the settings around it.

Company sign-in where it is free. Turn on Google or Microsoft sign-in in tools that offer it on your current plan.

A password manager for every tool that still has its own password, and for shared logins; shared accounts covers how to keep those under control.

A list of who has access to what. A spreadsheet works at first. It goes stale the week you stop updating it.

Roles, written down. "Engineer gets GitHub, Linear, Slack, Figma (viewer)." Five or six roles cover most small companies.

A leaver process that runs on the day, tool by tool (employee offboarding checklist).

A quarterly access review, an hour long, with the list in front of you.

Enforced SSO only where something requires it: a customer contract, an auditor, an insurer, or a tool whose data would sink you if a former employee kept access.

Do small businesses need IAM? They already have it, in the sense that somebody decides who gets which account. The question is whether it is written down and done the same way every time, or held in one person's memory.

Tools by budget

Prices below are from each vendor's own pricing page as we read it on 27 October 2026. Check before you buy; they change.

$0 extra: what you already pay for

Google Workspace or Microsoft 365 as directory and login. Enforce MFA, and use "Sign in with Google" or Microsoft where tools allow it. Google Workspace can also act as a SAML identity provider for many apps, and its automated user provisioning covers up to 3 apps on Business Starter and up to 100 on Business Standard and above (Google help), as long as the tool itself supports it on your plan.

On the Microsoft side, Entra ID Free comes with Microsoft cloud subscriptions such as Microsoft 365, and it does more than people expect. Microsoft's Entra licensing page, read the same day, lists security defaults (MFA registration for all users, with no license needed), sign-in and audit logs, and automated user provisioning to SaaS apps on the Free tier. What it keeps for paid tiers is the fine control: Conditional Access, the rules that decide when and from where people can sign in, needs Entra ID P1, which the same page says is included in Microsoft 365 Business Premium. Built-in access reviews need Entra ID P2 or Entra ID Governance. Microsoft Entra ID pricing goes through the tiers, and Google Cloud Identity Free covers Google's free identity service for people who need a managed Google account without the rest of Workspace.

A spreadsheet and a calendar reminder for the access list and reviews complete the zero-cost setup.

Per-user identity providers

These add enforced SSO, MFA policies and, on some plans, provisioning:

ProductListed priceNotes
Microsoft Entra ID P1$7 per user a month, paid yearlyEntra ID Free also exists (pricing)
Okta Starter$6 per user a month, billed annually, $1,500 yearly minimumProvisioning (Lifecycle Management) is an add-on (pricing)
Okta Essentials$17 per user a month, billed annuallyIncludes Lifecycle Management
JumpCloud SSO package$11 per user a month billed annually, $13 monthlyIncludes user lifecycle management; 30-day trial (pricing)

For a 20-person company, Okta Starter is $1,500 a year because of the minimum, and Essentials is $4,080. More detail in Okta pricing, JumpCloud pricing and IAM tools for small businesses.

The cost that is not on these pages

An identity provider can only enforce SSO in a tool that accepts it, and most tools only accept it on their Business or Enterprise plan. Upgrading those tools usually costs more than the identity provider. That is the SSO tax; the calculator puts a number on yours. The same applies to automatic removal: SCIM is usually on the SSO plan or a higher one.

Flat-fee access management

Tools that manage who has access to what, without changing how anyone logs in. SmashSSO is one; it is described at the end of this post.

How much does IAM cost? For a small company, anywhere from nothing (your existing directory, a password manager, a written process) to tens of thousands a year once enforced SSO across every tool is priced in. Most of the difference is the tool upgrades, not the identity provider.

A worked example: 20 people, three setups

Take a 20-person company on Google Workspace, and price three ways of doing IAM for a year.

The no-extra-spend setup. Google Workspace as directory with 2-Step Verification enforced, Google sign-in wherever tools offer it, and a password manager for the rest. Bitwarden Teams lists $4 per user a month billed annually (Bitwarden business pricing, read on 27 October 2026), so 20 people cost $960 a year. Access lists and reviews live in a spreadsheet. Cheap, and only as good as the person keeping the spreadsheet.

The full enforced-SSO setup. Okta Essentials at $17 a user is $4,080 a year. Then the tools: GitHub alone, moving from Team at $4 to Enterprise at $21 per user a month per GitHub's pricing page the same day, adds another $4,080 a year for 20 people, and every other tool you connect adds its own upgrade. Across a handful of common tools, the upgrades dwarf the identity provider.

The middle route. Keep the no-extra-spend setup for login, add a flat-fee access management tool for the access list, joiners, movers and leavers, and buy enforced SSO only for the one or two tools a customer contract names.

None of these is right for everyone. The point of pricing them is to see that "IAM" is not one purchase; it is a set of choices about which problem you pay to solve.

Contractors, guests, shared and service accounts

The awkward identities cause most of the access you cannot account for.

Contractors should get a directory account wherever possible, with an end date written next to it. If they cannot, list their tool accounts separately and put them on the same leaver checklist.

Guests, such as clients invited into a shared channel or project, live inside individual tools and never touch your directory. Review them in each tool's member list, and remove them when the project ends.

Shared accounts, like the company social media login, belong to no single person. Keep them in a shared vault, name an owner for each, and rotate the password when anyone with access leaves.

Service accounts and API tokens let tools talk to each other. Name an owner for each, and check during offboarding that none of them belonged to the person leaving, because a token outlives its creator.

The process that matters more than the tool

A perfect identity provider does not help if nobody removes the leaver from the design tool it is not connected to. These habits do more than any product.

Joiners: start from the role. When someone is hired, look up their role's list and create those accounts, with those roles. Nothing more "just in case". This is least privilege without the jargon.

Movers: remove as well as add. When someone changes team, take away the old team's tools. This is the step everyone skips, and how long-serving staff end up with access to everything.

Leavers: same day, every tool. Suspend in the directory first, then remove from each tool, transfer ownership of files, and revoke API tokens. Do it from a list, not from memory.

Owners for every tool. One named person per tool who can answer "who should be in here?"

Review quarterly. Compare each tool's member list to the directory. Accounts that match nobody are either leavers or orphaned accounts; both should go.

Keep a record. What changed, when, and who approved it. Auditors and customers ask for this, and it settles arguments.

None of this needs an Enterprise plan. It needs one list that stays true, and a way to act on it across every tool quickly.

Common IAM mistakes in small companies

Buying the identity provider first. It solves login, which was not the urgent problem. Start with MFA and the access list, then decide what to buy.

Letting tools in without an owner. Every tool someone signs up for with a company card becomes access you have to manage. Shadow IT covers how to find the ones you missed.

Handing out admin rights for convenience. The person who set up a tool is often still its owner years later, after changing jobs twice. Review admin roles separately from ordinary accounts.

Skipping movers. Leavers get attention because they are visible. Movers quietly collect access from every team they have been in.

What to do this week

Enforce MFA on your directory, admins first. Make the list: one row per tool, with every account and its role, matched against your directory. Write down five roles and the tools each one gets. Remove anything that matches nobody. That is a working IAM setup for a small company, and it costs an afternoon.

Where SmashSSO fits

SmashSSO covers the access part of IAM, the part your directory and your identity provider leave to you. It is not SSO and does not change how anyone signs in; for enforced login through an identity provider, you need real SSO.

It builds the access list for you. It reads your people from Google Workspace with read-only directory access and shows an access grid: who has an account in each tool, with what role, matched by email. Accounts that match nobody in the directory are flagged.

It handles joiners and movers by role. Access bundles such as "Engineer" invite a person to every tool in the bundle with the right role. Role changes run the same way.

It handles leavers. When someone is suspended in Google Workspace, it alerts you and shows every tool where they still have access, then removes them.

It keeps control and a record. Any step that would add a paid seat pauses for approval, and every change goes into an audit log.

Changes run through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, in tabs where you are already signed in as an admin. The honest limits: that agent needs the browser open, is slower than an API, and can fail when a tool redesigns its screens (a failed run says so and shows its last screenshot); some tools' terms restrict automated use; it needs Google Workspace as the directory; it has no SOC 2 or ISO 27001 report, no spend tracking and no CSV export.

It costs a flat fee from $199 a month billed annually, however many people and tools (pricing). How it works shows the grid and the bundles, and the SaaS management guide covers the wider job of keeping track of every tool you pay for.

FAQ

What is IAM?
Identity and access management: keeping track of who your people are, deciding what each of them can reach, and changing that when they join, move or leave. For a small company it means a directory, a way to log in, a record of who has access to which tool, and regular reviews.
What is the difference between identity management and access management?
Identity management answers who someone is: their account, their password, MFA and single sign-on. Access management answers what they can reach: which tools they have accounts in, with what role, and how that changes over time. Small companies usually handle the first well and the second badly.
Do small businesses need IAM?
They already do it, because someone decides who gets which account. What they need is to do it the same way every time: one directory, MFA, a written list of roles, same-day removals and a quarterly review. An enterprise IAM platform is optional.
What are IAM tools?
Directories such as Google Workspace or Microsoft 365, identity providers such as Okta, Microsoft Entra ID or JumpCloud that add SSO and provisioning, password managers, and access management tools that track and change who has access to each app.
How much does IAM cost?
From nothing extra, using the Google Workspace or Microsoft 365 you already pay for, to several dollars per user a month for an identity provider such as Okta or Entra ID P1. The bigger cost is usually upgrading each tool to the plan that accepts SSO.

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