Skip to content

Blog

SSO vs a password manager: which problem are you solving?

SSO vs password manager: one replaces passwords, the other stores them safely. What each solves, what each costs a small team, and why neither removes leavers.

· 9 min read

SSO vs password manager comes down to which problem you are solving. A password manager stores a separate password for every tool and fills it in for you. SSO gets rid of those passwords, by letting one company account log people in to every connected tool. One makes many passwords bearable; the other replaces them with one login you control.

Most small teams need a password manager whether or not they have SSO, because some tools will never support SSO on a plan they can afford, and every company has shared logins. And neither one, on its own, removes a leaver from your tools.

What each one does

A business password manager (1Password, Bitwarden and others) gives each person an encrypted vault for their logins, plus shared vaults for the team. It generates strong, unique passwords, fills them in, and lets an admin share a login with a group without anyone pasting it into a chat. The tool on the other end does not know a password manager exists. It sees a normal password login.

SSO (single sign-on) changes the login itself. The tool stops checking a password and instead accepts a signed statement from your identity provider, such as Google Workspace, Microsoft Entra ID or Okta, that says who the person is. There is no tool password to store, share or leak. What SSO is explains the pieces, and how SSO works follows a single login from click to signed-in.

Password managerSSO
Passwords per toolOne each, strong and storedNone for connected tools
Works with any toolYes, anything with a login formOnly tools that support SSO on your plan
Who controls the loginThe toolYour identity provider
Enforce MFA centrallyFor the vault; each tool sets its ownYes, at the identity provider
Shared loginsYes, through shared vaultsNo; SSO is per person
Leaver loses accessLoses the vault, but may remember or have copied passwordsCannot start new logins; accounts stay

The core difference: with a password manager, the tool still has a password that works for whoever holds it. With SSO, the tool has no password at all for that person.

Where they overlap

They meet in three places.

Password-vault "SSO". Some identity providers and portals store passwords for tools that do not support real SSO and fill them in when you click the tool's tile. It feels like single sign-on, but underneath it is a password manager. Types of SSO explains why it is not the same thing.

Unlocking the password manager with SSO. Business password managers can let people sign in to their vault through your identity provider. As we read their pages on 27 October 2026, 1Password's help center describes Unlock with SSO for 1Password Business accounts, and Bitwarden offers login with SSO, over SAML 2.0 or OpenID Connect, to Enterprise organizations. Bitwarden is explicit that the identity provider handles authentication while decryption of the vault is handled separately, and that the identity provider never gets the key to decrypt vault data.

Provisioning the password manager. The better business plans can create and suspend vault accounts from your directory. 1Password says Business can automate provisioning and that deprovisioning someone in your identity provider suspends them in 1Password. Bitwarden's help center says Teams and Enterprise organizations can use SCIM.

Some identity providers go the other way and bundle a password manager in. JumpCloud's pricing page, read the same day, describes its SSO package as "SSO & MFA access to resources plus Password Manager", at $11 per user a month billed annually (JumpCloud pricing; our JumpCloud breakdown).

So the password manager often becomes one more app behind your SSO, not a replacement for it.

Costs side by side

Prices below are from each vendor's own page, read on 27 October 2026, a month: per user unless the row says otherwise.

ProductPriceBillingRelevant details
1Password Teams Starter Pack$24.95 for 10 peopleBilled yearlyUp to 10 more seats at $4.99 each
1Password Business$8.99 per userBilled yearlyUnlock with SSO; automated provisioning
Bitwarden Teams$4 per userBilled annuallyDirectory sync; SCIM provisioning
Bitwarden Enterprise$6 per userBilled annuallyAdds SSO login and enterprise policies

Sources: 1Password business pricing, Bitwarden business pricing. Both offer free trials. 1Password's page disagrees with itself on the Starter Pack: the price card says "$2.49 / user", while its FAQ gives the flat $24.95 a month for 10 members used above. Confirm with 1Password before you budget.

Now compare SSO. The identity provider may be free if you use Google Workspace or Microsoft 365, or a per-user fee for a dedicated one: Okta's cheapest suite is $6 per user a month billed annually, with a $1,500 annual minimum, per Okta's pricing page the same day. The larger cost is in your tools. Most only accept SSO on a Business or Enterprise plan, so you upgrade every seat in every tool you want to connect. That is the SSO tax, and for a small team it is usually many times the price of a password manager. The SSO tax calculator works out your number.

A worked example: 15 people

Take a 15-person company. Bitwarden Teams for everyone is 15 × $4 × 12, or $720 a year. 1Password Business is 15 × $8.99 × 12, or $1,618.20 a year. Now put a single tool behind SSO: GitHub lists Team at $4 per user a month and keeps SAML SSO for Enterprise at $21, per GitHub's pricing page as we read it on 27 October 2026. Moving 15 people up costs 15 × $17 × 12, or $3,060 a year, for one tool. GitHub Enterprise pricing goes through that jump in detail.

So, is a password manager cheaper than SSO? Yes, by a wide margin, for most small teams. It also does less: it makes passwords safer instead of taking them away.

Password manager for business: what to look for

If you are choosing one, a handful of features decide whether it helps when people come and go. Look for shared vaults with group permissions, so the marketing logins go to the marketing group and nobody else. Look for admin account recovery, so a forgotten master password does not lose the company's logins with it. Look for a way to suspend someone centrally and see what they could reach, because that list is what you rotate from when they leave. SSO unlock and SCIM provisioning are worth paying for once you have an identity provider that can use them. And check that it can require MFA on the vault itself, because the vault is now a single point of attack in the same way an identity provider is.

The leaver problem neither solves

Here is the trap. Someone leaves. What does each tool do?

The password manager suspends their vault. Good. But they may still know passwords: anything they typed, saw or copied out of the vault still works until you change it. Shared logins are exposed, and every shared password they had access to should be rotated; most teams do not, because nobody has a list. And their own accounts still exist. Their Slack, GitHub and Figma accounts are not touched by the password manager. It never knew those accounts belonged to your company.

SSO stops new logins. Better. But the accounts stay: every tool keeps the account, often with a paid seat, until someone removes it. Open sessions keep working until they expire, for reasons how SSO works explains. And tools outside SSO are untouched, which are exactly the ones in the password manager.

Can a password manager offboard people? It can offboard them from the password manager. Removing their accounts in your other tools is a separate job, called deprovisioning; see what deprovisioning is and our employee offboarding checklist.

A sensible setup for a small team

For a 5 to 50 person company on Google Workspace or Microsoft 365, the order below covers most of the risk for little money.

Enforce MFA first, on Google Workspace or Microsoft 365. It protects every "Sign in with Google" or "Sign in with Microsoft" login at once, and SSO vs MFA explains why this comes before anything else.

Use "Sign in with Google" or "Sign in with Microsoft" in every tool that offers it on your current plan. It is SSO in practice, if not enforced, and free.

Buy a business password manager for everything else, and put every shared login in a shared vault, not a spreadsheet or a chat. Shared accounts covers how to handle those.

Keep a list of who has which account in which tool, and work through it when someone leaves. Rotate the shared passwords they could see.

Add enforced SSO only where it is required: a customer contract, an auditor or a real risk that justifies the tool upgrade.

What about shared passwords under SSO? SSO is per person, so a shared login (the company social media account, the domain registrar) cannot go behind it. Those stay in the password manager, with MFA where the tool allows it, and get rotated when someone with access leaves.

Contractors are the other edge case. If they do not get an account in your Google Workspace or Microsoft 365, they cannot use your SSO or your company sign-in at all, so whatever they reach goes through passwords. Give them access in the password manager to only the vault they need, and put their accounts on the same leaver list as everyone else's. Contractor access management covers the rest.

Where SmashSSO fits

SmashSSO is neither a password manager nor SSO. It stores no passwords, fills nothing in and does not sit in anyone's login.

It keeps the list from the setup above. It reads your people from Google Workspace with read-only access, shows who has an account in each tool and with what role, and flags accounts that match nobody in your directory. When someone is suspended in Google Workspace, it alerts you and shows every tool where they still have access, and removes them through the tool's member API where you have added a token, or through an agent in your own Chrome, in tabs where you are already signed in as an admin. That browser has to be open, agent runs can fail when a tool changes its screens, and some tools' terms restrict automated use. It does not rotate shared passwords; that stays a job for you and your password manager.

It costs a flat fee from $199 a month billed annually (pricing). If you need enforced login through an identity provider, you need real SSO for those tools.

FAQ

Do I need a password manager if I have SSO?
Almost certainly. SSO only covers tools that support it on your plan, and shared logins such as a social media account or the domain registrar cannot go behind it. A password manager handles everything SSO does not reach.
Is a password manager cheaper than SSO?
Yes, by a wide margin for most small teams. As read on 27 October 2026, 1Password Business is $8.99 and Bitwarden Teams $4 per user a month, billed yearly. SSO usually means upgrading every seat in each tool to a higher plan, plus an identity provider if you lack one.
Can a password manager offboard people?
Only from the password manager itself. Business plans can suspend a vault when someone is removed from your identity provider, but their accounts in Slack, GitHub and other tools stay, and any passwords they saw keep working until you change them.
What about shared passwords?
Keep them in a shared vault in your password manager, not a spreadsheet or chat, with MFA on the account where the tool allows it. SSO cannot cover a login shared by several people, and every shared password a leaver could see should be rotated.

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