# Troubleshoot SSO errors
If your Redox organization is enabled for single sign-on (SSO), you may run into some of these errors.
But first, here are the SSO glossary terms for your reference:
Identity provider (IdP)
A third-party system that stores and manages users in your organization. This is useful for anyone that wants to enable SSO for their Redox organization. [Learn how to set up SSO](/how-to-use-redox/manage-your-redox-setup/set-up-sso-login-to-the-redox-dashboard) for your organization.
Some examples of common **identity providers** are Okta, Jumpcloud, Entra, or OneLogin. [Read TrustBuilder‘s docs about identity providers](https://www.trustbuilder.com/what-is-identity-provider).
IdP-initiated login
In terms of SSO, you can initiate a login through your **identity provider** (**IdP**) or the **service provider** (**SP**) can initiate a login.
If SSO is configured to be **IdP-initiated**, it means you must click somewhere in the app to launch SSO login for the service provider.
Some examples of IdP-initiated login are Gmail, Slack, and Salesforce.
Service provider (SP)
A vendor or site that someone wants to log into in order to perform some type of action.
In the Redox world, the Redox dashboard is an example of a **service provider**. Authentication and user management is handled by the **identity provider**.
SP-initiated login
In terms of SSO, you can initiate a login either through your identity provider (IdP) or the service provider (SP) can initiate a login.
If SSO is configured to to be SP-initiated, it means that the vendor or website launches SSO login on your behalf.
An example of SP-initiated login is the Redox dashboard.
## Unable to log in
You or a user in your organization isn’t able to log in to your Redox organization via SSO.
First, make sure that you’re not trying to log in to Redox from your identity provider (IdP). Redox only supports an SP-initiated login, meaning you should log in via the Redox dashboard, which launches the SSO workflow.
To verify, [log in to the Redox dashboard](https://dashboard.redoxengine.com/#/login) directly after it’s been configured and enabled for your organization.
## Error message or timeout
You or a user in your organization sees an error or the SSO request times out when you try logging in to your Redox organization.
Make sure that you’ve entered the configuration settings correctly both in the Redox dashboard and the IdP. [Review how to set up SSO](/how-to-use-redox/manage-your-redox-setup/set-up-sso-login-to-the-redox-dashboard).
> **Redox Sign-in URL vs. IdP Sign-in URL**
>
> You must enter a **Sign-in URL** in both the Redox dashboard and your IdP, but these URLs shouldn’t be the same.
>
> - The Sign-in URL in the Redox dashboard _should point to your IdP_.
> - The Sign-in URL in the IdP _should point to the Redox dashboard_.
## New users not showing up
You may see a user in your IdP but not in the Redox organization (whether in the dashboard or via the Platform API).
Remember that SSO-enabled organizations must first add a user in your IdP. Then, the new user must log in to the Redox dashboard, which triggers a sync between the IdP and Redox. If you’re not seeing a user in the Redox organization, it’s likely that the user hasn’t tried logging in to the Redox dashboard yet.
## Unable to see invitations in the dashboard
You’re unable to see the Invitations tab on the Users page of the Redox dashboard.
This is expected if you’re part of an SSO-enabled organization. Since you add users to your Redox organization via your IdP, you don’t need the typical invitation flow that other non-SSO organizations use. So, the Invitations tab is purposefully hidden.
*No invitations for SSO-enabled organizations*
*Invitations for non-SSO orgs *
> **SSO articles**
>
> For more info about SSO, review these articles:
>
> - [App launch within an EHR system via SSO](/basics/handling-app-launch-sso-from-ehr-systems)
> - [Set up SSO for your organization](/how-to-use-redox/manage-your-redox-setup/set-up-sso-login-to-the-redox-dashboard)
> - [Launch app within an EHR system](/fhir-api-actions/authentication-and-app-launch/launch-app-within-an-ehr-system)