Built LMS Help Center
Settings

Map OIDC Claims and Profile Fields

Configure email, name, and custom field claims for an OIDC provider.

Use this guide after the OIDC provider connection exists and before pilot testing. Built LMS requires a stable email claim for profile matching.

Before you begin

You need:

  • A saved OIDC provider in Built LMS.
  • Access to the IdP app's claim or token configuration.
  • A pilot user assigned to the IdP app.
  • Any Built LMS custom user fields you want to map already created.

Do not map a claim unless the IdP is the right source of truth for that value.

Confirm claim mapping

Built LMS reads these standard OIDC claims:

Built LMS user fieldOIDC claimRequired
EmailemailYes
Display namenameNo
First namegiven_nameNo
Last namefamily_nameNo

The email claim must be stable and present for the pilot user. If the IdP sends a different email than the user's Built LMS profile, the sign-in can create or match the wrong identity.

If the IdP requires explicit claim configuration, configure the app to include:

  • sub
  • email
  • email_verified when available
  • name
  • given_name
  • family_name

Map custom user fields

Use custom field mappings only for claims that should update on each SSO login.

  1. In the OIDC provider form, find Custom field mappings.
  2. Select Add mapping.
  3. Enter the OIDC claim name.
  4. Select the Built LMS custom user field.
  5. Repeat for each field.

The mapping list is available only when active custom user fields exist in the organization.

Good candidates:

  • department
  • employeeType
  • manager
  • managerEmail
  • costCenter

Claim names must match exactly. If the IdP nests claims or uses namespaced claims, copy the exact claim name your IdP emits.

Verify success

Claim mapping is ready for pilot testing when:

  • The IdP app sends email for the pilot user.
  • profile and email scopes are requested when name and email claims are expected.
  • Optional name claims appear when your team expects them.
  • Custom claim names match exactly.
  • Active Built LMS custom user fields exist for every mapped field.

Troubleshooting

On this page