Single Sign-On for Internal Business Apps: What It Solves and How to Roll It Out
November 11, 2026 · 7 min read · Etzal Group Team
An employee leaves a 60-person company on a Friday. HR removes the email account. Three months later, during an audit, someone notices that the same person can still log in to the CRM, the project tool, the accounting package and the file storage, each of which had its own username and password that nobody remembered to remove. Nothing bad happened, this time. Single sign-on exists largely to make that story impossible.
The problem
As a company adopts more software, each application arrives with its own login.
- Staff juggle a dozen passwords, reuse them and write them down.
- IT creates accounts in every system for each new hire, resets forgotten passwords daily, and must remember every system when someone leaves.
- Security depends on the weakest of those logins, and on nobody forgetting one.
- Nobody can say with confidence who has access to what.
What single sign-on does
A central service, the identity provider, holds each person's account. Applications, called service providers, stop keeping their own passwords and instead ask the identity provider, "who is this?"
The experience:
- The person opens an application.
- The application sends them to the identity provider.
- If they have already signed in today, they are sent straight back, recognised. If not, they sign in once, with a second factor.
- The application lets them in.
One sign-in, many applications. And one account to switch off.
What it gives you
- Offboarding in one step. Disable the central account, and access to every connected application ends.
- Onboarding in one step. Create the account, assign groups, and the right applications are available.
- Multi-factor authentication everywhere. Enforce it once at the identity provider, including for applications that offer none of their own.
- Fewer passwords. Fewer resets, less reuse, less phishing surface.
- Central policy. Password rules, session length, sign-in only from managed devices or certain countries.
- One audit trail. Who signed in to what, when, from where.
The terms you will hear
Identity provider, IdP. The central service that authenticates people. Often part of the email and office suite a company already has.
SAML. An older, widely supported standard for single sign-on to business applications. Common in enterprise software.
OpenID Connect, OIDC. A more recent standard built on OAuth 2.0. Common in modern web and mobile applications.
OAuth 2.0. A standard for granting an application limited access to something on a user's behalf. It is about authorisation. OpenID Connect adds the identity part.
SCIM. A standard for creating, updating and removing user accounts in applications automatically. Single sign-on controls who can sign in. SCIM controls whether the account exists at all.
MFA. Multi-factor authentication: something beyond a password, such as an authenticator app, a passkey or a hardware key.
You do not need to master these. You need to ask of each application: does it support SAML or OpenID Connect, and does it support SCIM?
What single sign-on does not do
- It does not decide what a person may do inside an application. That is authorisation, managed by roles in each application, sometimes fed by groups from the identity provider.
- It does not remove accounts by itself. After the central account is disabled, the person cannot sign in, but their account and data may remain in the application until provisioning or a manual step removes them.
- It does not end existing sessions everywhere at once. Someone already signed in to an application may stay signed in until the session expires. Know the session lengths, and how to revoke sessions for urgent cases.
- It does not cover applications that do not support it.
Rolling it out
1. Choose the identity provider
Usually the one you already have with your email and office suite. Check that it supports the standards your applications need, multi-factor authentication, and groups.
2. Make the directory right
Single sign-on is only as good as the list of people behind it.
- Every employee has exactly one account.
- Leavers are disabled promptly. Tie this to HR's process.
- Groups reflect real teams and roles.
- Shared and generic accounts are identified and reduced.
3. Turn on multi-factor authentication
Before connecting applications. Prefer methods resistant to phishing, such as passkeys or hardware keys, for administrators and anyone with access to money or sensitive data. Authenticator apps are a sound baseline. SMS codes are the weakest option.
4. Connect applications in order of risk
Make an inventory: every application, who uses it, what data it holds, whether it supports single sign-on.
Then connect in this order:
- Applications holding financial, customer or employee data.
- Applications used by everyone.
- The rest.
For each: connect, test with a small group, switch everyone over, then disable password login in that application. An application that still accepts its old passwords has gained a door, not lost one.
5. Handle the exceptions
- Applications without support. Keep them in a password manager with strong, unique passwords, restrict who has access, and review them at each offboarding. Prefer alternatives that support single sign-on when renewing.
- Service accounts and integrations. Not people. Give them their own credentials, limited permissions, and an owner.
- Emergency access. One or two "break glass" administrator accounts that do not depend on the identity provider, with long random passwords stored securely and alerts on any use. If the identity provider is down, you still need a way in.
- External users. Contractors, auditors, partners. Give them accounts with an end date.
The cost question
Many software vendors include single sign-on only in their more expensive plans. This can change the price of a tool considerably.
- Ask about it before buying, not after.
- Include it when comparing products.
- For applications where the upgrade is not justified, use the exceptions approach above and accept the gap knowingly.
For custom-built applications
When commissioning internal software, require it from the start.
- Authentication through your identity provider using OpenID Connect or SAML. The application should not store passwords at all.
- Roles mapped from groups in the identity provider where practical.
- Sessions that respect central sign-out and have a sensible lifetime.
- Automatic account creation and deactivation, by SCIM or at first sign-in with a scheduled check against the directory.
- An audit log of sign-ins and permission changes.
Adding single sign-on to an application built with its own login is possible and more work than doing it at the beginning.
Offboarding, properly
With single sign-on in place, the checklist shrinks and does not vanish.
- Disable the central account at the agreed time.
- Revoke active sessions.
- Remove or transfer ownership of files, mailboxes and shared resources.
- Check the exceptions list: applications outside single sign-on, shared passwords the person knew, API keys they created.
- Remove devices from management.
- Record that it was done.
Steps 1 and 2 used to be twelve separate tasks. Step 4 is the reason to keep the exceptions list short.
Measuring success
- Share of applications connected, weighted by sensitivity.
- Share of users with multi-factor authentication. The target is all of them.
- Time from an employee's last day to complete loss of access.
- Password reset requests per month.
- Accounts found in applications that belong to nobody current. This should fall to zero.
Common mistakes
- Connecting single sign-on without multi-factor authentication.
- Leaving password login enabled alongside it.
- A messy directory: duplicate accounts, leavers still active.
- No emergency account, then an identity provider outage locks everyone out.
- Forgetting sessions.
- Assuming it removes accounts.
- Ignoring the applications that cannot connect.
- Buying software without checking its single sign-on support and price.
We build internal systems that authenticate through the client's identity provider, and help companies bring existing applications under one sign-in, as part of Enterprise Software. If your offboarding still involves a list of twelve logins, contact us.
Summary
Single sign-on puts every application behind one account per person, held by an identity provider. Clean the directory, enforce multi-factor authentication, then connect applications in order of risk and switch off their own password logins. Keep emergency accounts, manage the exceptions deliberately, and remember that authorisation, account removal and active sessions still need attention. Require it in any software you buy or commission.
Frequently asked questions
What is single sign-on?
Single sign-on lets a person sign in once, with one account, and then open every connected application without signing in again. The applications trust a central identity provider to confirm who the person is. One account to create, one to protect with a second factor, and one to disable when someone leaves.
Is single sign-on less secure because one password opens everything?
It concentrates risk in one account, which is why that account must be protected with multi-factor authentication. With that in place it is generally safer than many separate passwords, which people reuse, write down and forget to change, and which linger in applications long after an employee has left.
Does a small company need single sign-on?
Once staff use more than a handful of business applications, or people join and leave regularly, it pays off. The clearest benefit is offboarding: disabling one account removes access everywhere. Many companies already have an identity provider through their email and office suite and are simply not using it for other applications.
Related service
Website Development
Fast, SEO-ready websites that turn visitors into customers.
