My Service Support

SSO for Enterprise: How to Sign In With SSO

Updated 2026-08-23 · 907 words

Be the first to rate this page

What is enterprise SSO?

Enterprise SSO, short for single sign-on, is an arrangement where your employer runs one identity system and every work application trusts it. You sign in once to that central system, and the applications let you in without asking for a separate password.

The practical consequence is the part people miss when something breaks: the application you are trying to open does not hold your password and cannot reset it. Your employer's identity system holds it, so that is where a fix has to come from.

How do I sign in with enterprise SSO?

  1. Open the application and look for a button worded as sign in with SSO, use single sign-on, or sign in with your organisation.
  2. Enter your work email address, or the company identifier the page asks for, and continue.
  3. You will be sent to your employer's own sign-in page. Check that the page shows your company name before typing anything.
  4. Enter your work credentials there and complete any second step, such as an approval in an authenticator app.
  5. You are returned to the application, already signed in. Nothing further should be asked.

If step three sends you somewhere that does not look like your company, stop. A genuine SSO redirect always lands on your employer's page, and one that does not is worth reporting.

What do I need before I start?

  • Your work email address in full, since the domain part is what routes you to the right company.
  • Your work password, not a personal one you may have used to try the app before.
  • The device that holds your second-step approval, usually a phone with an authenticator app.
  • The company identifier or workspace name, if the app asks for one instead of an email.
  • Any access request you already submitted, since SSO can succeed while the app still refuses you.

Why does the app say my organisation was not found?

This message means the application does not recognise the domain of the email you entered as one connected to SSO. There are three ordinary reasons.

The first is that you typed a personal address rather than the work one. The second is that your company uses more than one email domain and only one of them is connected. The third is that SSO has not been switched on for this application yet, in which case no user can sign in that way until an administrator configures it.

Try your primary work address exactly as it appears in your company directory. If that also fails, this is a configuration matter for your IT team, not something you can work around.

Why does SSO send me round in a loop?

A loop, where the app sends you to sign in and the sign-in sends you straight back, is usually caused by something small on your device. The most common causes are blocked cookies, a browser in strict privacy mode, an extension that interferes with redirects, or a session left over from a different account.

Try a private browsing window first. If the loop stops there, the cause is local: clear the cached data and cookies for both the app and your company sign-in page, then sign in again. If you are signed in to a personal account of the same service in that browser, sign out of it first, since two identities in one browser is a frequent cause.

If the loop happens for colleagues too, it is not your device and it should be reported.

What if SSO works on my laptop but not my phone?

Mobile applications often keep their own stored session, which goes stale without warning. Sign out inside the app completely rather than just closing it, then sign in again and let the redirect happen.

Check the obvious things too. An out-of-date app may no longer support the current sign-in method, and a device clock set manually to the wrong time breaks the security check the process depends on. Set date and time to update automatically.

If your company requires managed devices, a personal phone may be refused by design. The error rarely says so, but IT can confirm it in a sentence.

What if I changed roles or left the company?

SSO access follows your employment record, so a role change, a department move, or a leaving date can remove access from every connected application at once. That is intended behaviour rather than a fault.

If you still need the application, ask for it to be added to your access profile through whatever request process your company uses. If you have left, your work identity is gone and the account cannot be recovered by you. Anything personal in there has to be requested from the employer directly.

What should I tell the help desk?

A vague report gets a slow answer. Give them the application name, the exact wording of the error, the time it happened, the email address you used, the device and browser, and whether it fails everywhere or only in one place.

Add one more line that saves the most time: whether a colleague can sign in to the same application right now. That single fact tells the help desk whether they are looking at your account, your device, or the connection itself. If your company publishes its own guidance at the company’s official website, check it before raising the ticket, since many access requests have a defined form that is faster than a general query.

Was this page helpful?

Be the first to rate this page