Can't sign in with single sign-on? Common problems and fixes

If you cannot sign in with single sign-on (SSO), the email address you are using may not match the one your company set up. First, try your work email address, which uses your company's web address after the @ symbol (for example, you@yourcompany.com, not a personal email address).

The following are the most common error messages and how to resolve them.

This email is not configured for SSO

You may be using a personal or incorrect email address, or your company may not have added your account yet. Try signing in with your work email address. If the error continues, ask your company admin to confirm that your account is set up.

App not assigned

Your company's information technology (IT) team needs to give you access to Remote through your company's login system, such as Okta or Microsoft. Ask your IT team to give you access. Remote cannot do this for you.

Something went wrong with your company's SSO

This error usually means SSO was not set up correctly and no one can sign in. Your company admin should contact Remote and ask us to turn off SSO. To protect your account, Remote first confirms the admin's identity through a quick photo identification (ID) check. After Remote turns off SSO, you can sign in again and your company can set it up again.

You see a page full of code

This happens when the sign-in web address was entered incorrectly. Your admin should contact Remote and confirm their identity through a photo ID check. Remote can then turn off SSO so your company can set it up again with the correct address.

See also: How can I exempt SSO enforcement for company admins who can’t authenticate using SSO?