> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wejam.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Users After SSO Is Live

> What JAM Admins need to know once Enterprise SSO is on: the right login, roles of new users, enforcement, and exceptions.

## Overview

Once your IT team has connected JAM to your identity provider (see [Setting Up Enterprise SSO](https://docs.wejam.ai/external/admin/saml-oidc-setup.md)), day-to-day questions move to the JAM **Admin**: why a user sees a Microsoft permission screen, which role new users get, and what to do when someone cannot use SSO. This page answers those questions.

## Before you start

* You need the **Admin** role in JAM.
* SSO must already be live for your company's email domain.

## Point users to the right login

> [!WARNING]
>
> The **Sign in with Microsoft** button is **not** your company SSO. It is a
> generic Microsoft login and may ask for app permissions your IT team has not
> approved.

With SSO live, users sign in like this:

**1. Open app.wejam.ai**

Go to [app.wejam.ai](https://app.wejam.ai), or use the direct SSO address `auth.wejam.ai/login_sso`.

**2. Enter the work email**

JAM recognizes the company domain and sends the user to your company login.

**3. Sign in at your company**

After signing in with the company account, the user lands in JAM. There is no separate JAM password.

To skip the choice entirely, share one of the direct links in [Directing Users Straight to SSO](https://docs.wejam.ai/external/admin/saml-oidc-setup.md#directing-users-straight-to-sso-optional).

## Roles of new SSO users

* A person who signs in through SSO **without an invitation** joins as a **Learner** by default.
* If the person was **also invited** with a higher role, the higher role applies, so invite Coaches and Admins before the rollout.
* Change roles on the **Users** page - see [Assigning Roles to Users](https://docs.wejam.ai/external/admin/assigning-roles.md).
* Your identity provider can also set roles. To set this up, email [support@wejam.ai](mailto:support@wejam.ai).

## When SSO is enforced

After SSO is set up, members of your organization can only sign in through SSO. Everyone with an address on your email domain is sent to the SSO login. People whose account is in another JAM organization **without** SSO can still sign in there with the password login link - see [Accessing Multiple JAM Organizations](https://docs.wejam.ai/external/admin/multi-organization-access.md#one-organization-uses-sso-the-other-a-password).

If a person or a whole organization needs an exception, for example an external trainer or a test account, email [support@wejam.ai](mailto:support@wejam.ai) with the email addresses and the reason. JAM sets up the exception.

## Accounts for the setup only

The person who completes the SSO setup wizard needs a JAM account. If that was an IT colleague who will not use JAM, email [support@wejam.ai](mailto:support@wejam.ai) after the setup and JAM removes the account.

## Troubleshooting

> [accordion] Users see a Microsoft screen asking for app permissions
>
> They clicked **Sign in with Microsoft**. Ask them to enter their work email on [app.wejam.ai](https://app.wejam.ai) instead, or to use `auth.wejam.ai/login_sso`.

> [accordion] "AADSTS50105" or "app permission needed" in Microsoft Entra
>
> The user is not assigned to the JAM enterprise app. Group membership counts only if that group is assigned to the app. Your IT team fixes this - see [the AADSTS50105 entry](https://docs.wejam.ai/external/admin/saml-oidc-setup.md#aadsts50105).

> [accordion] A new user has the wrong role
>
> Users who join through SSO without an invitation are Learners by default. Change the role on the **Users** page.

> [accordion] Someone signed up without SSO, or ended up in the wrong organization
>
> Email [support@wejam.ai](mailto:support@wejam.ai) with the email address and the organization the person belongs in. JAM moves the account.

> [accordion] An employee left the company
>
> Remove the person in your identity provider, and delete the user on the **Users** page to free the seat - see [Creating and Managing User Accounts](https://docs.wejam.ai/external/admin/managing-user-accounts.md).

> [accordion] A person needs access to two JAM organizations
>
> One email address can be active in one organization only. With SSO, the person needs a second SSO account or an SSO exception - see [Accessing Multiple JAM Organizations](https://docs.wejam.ai/external/admin/multi-organization-access.md).

## Related articles

* [Setting Up Enterprise SSO](https://docs.wejam.ai/external/admin/saml-oidc-setup.md) - the setup for your IT team
* [Fixing Invitation and First-Login Problems](https://docs.wejam.ai/external/admin/invite-and-login-troubleshooting.md) - when a new user cannot get in
* [Assigning Roles to Users](https://docs.wejam.ai/external/admin/assigning-roles.md) - what each role can do
* [Accessing Multiple JAM Organizations](https://docs.wejam.ai/external/admin/multi-organization-access.md) - one person in several organizations

***

*Last updated: October 2026*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.