All articles

Single Sign-On Setup: A Plain Guide for Business Owners

How to set up single sign-on: what to gather first, SAML or OIDC, step-by-step configuration, testing, lockout protection and when to build SSO into your app.

Single sign-on (SSO) lets your team log in to many apps with one set of credentials, checked by one identity provider. To set it up, list your apps, pick the identity provider, verify your domain, connect each app, test with a pilot user, and only then require it for everyone. Keep a backup admin login the whole time. If you sell software and a customer asks for SSO, the work is different: you add SSO to your product, and we cover that below.

TL;DR

  • Start with an app inventory and a named owner. Setup goes wrong most often before any configuration begins.
  • Use the identity provider you already have, such as Google Workspace or Microsoft Entra ID, before paying for another one.
  • Choose OIDC for new web and mobile apps. Choose SAML when a customer or an older system asks for it.
  • Pilot with one or two accounts, and keep a break-glass admin login so you cannot lock yourselves out.
  • If you are adding SSO to your own product, build it when a real deal needs it, not before.

What you need before you start

Most setup guides jump straight to the settings page. Skip ahead too fast and you will stall on a missing permission or a DNS record.

Gather these first:

  • An app inventory. Write down every tool your people use, including the ones nobody officially owns.
  • Who does what. Name one person for planning, one for technical configuration, one for user management and one for policy. In a ten-person company that may be two people. That is fine.
  • Admin access to your identity provider (the service that confirms who a person is, such as Google Workspace or Microsoft Entra ID).
  • Control of your company domain's DNS. Many apps ask you to prove you own the domain by adding a text record. Square's help center says its DNS verification can take up to 72 hours to replicate, so start this early.
  • The right plan on each app. Many apps only offer SSO on a higher tier. Contracko's documentation is one example: SSO settings sit on its top plan only.

For each app, record the SSO protocol it supports, the plan that unlocks it, the admin role you need, and how it handles removing a user. That small spreadsheet saves hours.

The U.S. cybersecurity agency CISA studied small business adoption. Its 2024 report on SSO barriers for small and midsize businesses names cost, training needs, vendor lock-in and lack of technical knowledge as the main obstacles. A short plan up front addresses most of them.

SAML or OIDC: which one to pick

Both are ways for your identity provider to tell an app, "yes, this person is who they say they are." SAML is the older, XML-based standard. OIDC (OpenID Connect) is newer and built on OAuth 2.0. Microsoft's decision guide describes SAML 2.0 as a mature federation protocol and OIDC as a modern one using JWTs and REST APIs.

The practical rule from the same guide: use OIDC for new SaaS, web, mobile and single-page apps. Use SAML when enterprise customers, older identity providers or procurement rules call for it. Where your customers have mixed setups, support both.

The U.S. government's Enterprise Single Sign-On Playbook treats both as standard ways to pass identity assertions between systems. If you want a developer-level walk-through of SAML specifically, these SAML SSO setup steps for SaaS lay out what product teams need to cover.

Setting up SSO step by step

1. Pick your identity provider

Shortlist two or three at most. Include the one you already pay for. If your team lives in Google Workspace or Microsoft 365, test that first, because there is nothing new to buy or learn.

2. Verify your domain

Add the text record the app gives you at your DNS host. Then wait. This is the step that makes people think something is broken. Contracko notes propagation can take up to 48 hours.

3. Create the connection

In the identity provider, add the app. In the app, paste in what the provider gives you. For SAML that is typically an Entity ID, a sign-in URL and a certificate. Zapier's SAML setup page lists exactly those, and says the email field must use the SAML emailAddress format. The Enterprise SSO Playbook adds a useful rule: pass only the minimal identity attributes the app needs. Usually that is name and email.

4. Plan for user changes

SSO only helps with offboarding if removed people lose access everywhere. Where an app supports automatic provisioning (SCIM), use it. Wistia's documentation shows the idea: deactivate a user in the identity provider and they are deprovisioned in the app. The government playbook recommends testing provisioning and deprovisioning to confirm access is revoked on time.

5. Pilot with one or two accounts

Test login with a non-admin account. Check that the right name and email arrive. Then test removal. Square recommends trying SSO with individual accounts before switching it on for the whole business. CISA's study likewise recommends a pilot before full rollout.

6. Roll out and train

Tell people the day it changes and what the login screen will look like. Ten minutes of explanation prevents a week of "I can't get in" messages.

Protect yourself from lockout

Turning on required SSO can change how every account logs in. Square's page warns that enabling it affects everyone on verified domains and can remove passwords and passkeys from SSO-only accounts, so set up backup break-glass accounts first.

Some apps build this in. Wistia's required mode keeps password fallback for the account owner and admins, so a broken connection does not shut you out.

Two more habits help:

When something fails

The playbook's troubleshooting advice is simple and works for small teams. Check the logs in both the identity provider and the app. Check certificates and attribute mappings. Try a known-good app to see whether the problem is the connection or the one app. Test in a non-production setup when you can, so a fix does not hit live users.

Most first-time failures come from three things: a mismatched email format, an expired or wrong certificate, and a domain that has not finished verifying.

If you are adding SSO to your own product

This is a different job. You are not connecting tools to a login. You are making your app accept logins from your customers' identity providers.

Three questions settle most of it:

  1. Is a customer asking? Enterprise buyers with an IT team often require SAML or OIDC sign-in. Until that happens, email, social or passwordless login is usually enough.
  2. Which protocol? For a new product, OIDC. Add SAML when a customer's setup needs it.
  3. Who handles the edge cases? Provisioning, logout, session length and account linking take more time than the first successful login.

These choices touch your login screen, your user model and your admin settings. They are easier to plan before the app is built than after. If you run a dealer portal, a membership site or a SaaS product, decide early who your customers are and how they sign in.

This is also where a first-time founder without a technical co-founder can lose weeks. A short scoping conversation on the login model usually costs less than reworking it later.

For real estate and property teams the same logic applies on a smaller scale: one login across your CRM, listing tools and tenant systems means fewer forgotten passwords and a cleaner exit when someone leaves. Our property management automation playbook shows how we think about connecting those tools.

Our perspective

Most of the SSO trouble we hear about is planning trouble. A team picks a provider first, then finds out half its tools lock SSO behind a higher plan.

We build custom websites, apps and web platforms, including dealer and membership portals. When login is part of a build, we want to settle it at the start: who signs in, from which accounts, and what happens when they leave. Our approach is hands-on and open. You see the decisions as we make them.

Our advice to business owners is plain. Use the identity provider you have. Pilot with two people. Keep a backup admin. Then widen the rollout.

Loic

Need SSO built into an app or portal?

We design and build custom apps and web platforms for startups, B2B distributors, SaaS founders and local businesses in Canada and the US. If your customers need to sign in with their own company accounts, we can scope that with you from the first conversation and keep you involved through launch. See our app development service or the full list of services.

FAQ

How long does single sign-on setup take?

The configuration itself can take an afternoon per app. The waiting is DNS verification, which Square says can take up to 72 hours. Plan a pilot week and a rollout week for a small team.

Do I need SSO for a small business?

Not for every tool. Start with the apps that are used most often or hold sensitive data, and the ones where offboarding matters. CISA's research suggests starting with a pilot and relying on vendor guidance during the first rollout.

Is SAML or OIDC better?

For new web and mobile apps, Microsoft recommends OIDC. SAML is the right choice when a customer or an older system requires it. If your customers vary, support both.

What if an app does not support SSO?

You cannot force it. Give each person a named account, keep credentials in a business-managed password manager, turn on the app's own multi-factor sign-in where it exists, and include the app when someone leaves.

How do I avoid locking out my admins?

Create break-glass admin accounts before you require SSO, and test them. Some apps, such as Wistia in required mode, keep password fallback for owners and admins.

Sources

Written by westcode.io, an independent studio in Kelowna and Vancouver.

AI & automation8 min read

Answer Engine Optimization: A Practical Guide for Business Owners

Answer engine optimization explained for business owners: how AEO differs from SEO, the steps that earn AI citations, and how to measure results in Search Console.

AI & automation7 min read

Technical Debt Management: A Practical Plan for Business Owners

Technical debt management for non-technical owners: what it is, how to rank fixes, how much time to set aside, and how to build a simple roadmap.

AI & automation5 min read

What is an AI agent? A plain answer for Canadian businesses

What an AI agent actually does, how it differs from a chatbot, what Canadian businesses use them for, and what a real build costs in 2026.