Skip to main content

Overview

Once your IT team has connected JAM to your identity provider (see Setting Up Enterprise SSO), 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

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, 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.

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.
  • Your identity provider can also set roles. To set this up, email 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. If a person or a whole organization needs an exception, for example an external trainer or a test account, email 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 after the setup and JAM removes the account.

Troubleshooting

They clicked Sign in with Microsoft. Ask them to enter their work email on app.wejam.ai instead, or to use auth.wejam.ai/login_sso.
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.
Users who join through SSO without an invitation are Learners by default. Change the role on the Users page.
Email support@wejam.ai with the email address and the organization the person belongs in. JAM moves the account.
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.
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.

Last updated: October 2026