Built LMS Help Center
Settings

Map SAML Attributes and Profile Fields

Send email, names, and custom user fields from a SAML identity provider into Built LMS.

Use this guide after the SAML provider exists and you need Built LMS to receive the right user identity and profile data from the IdP.

Before you begin

You need:

  • A saved SAML provider in Built LMS.
  • Admin access to the SAML app in the IdP.
  • The IdP source fields for email, first name, last name, and any profile fields you want to sync.
  • Active Built LMS custom user fields, if you plan to map custom fields.

Configure required identity attributes

Step 1: Send email as NameID

Configure the SAML Subject NameID to use the user's email address.

Use:

urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

Email is the important field. If the IdP sends a different email than the user's Built LMS profile, the sign-in can create or match the wrong identity.

Step 2: Send standard profile attributes

Configure the IdP to send:

Built LMS user fieldSAML attributeRequired
EmailemailYes
First namefirstNameNo
Last namelastNameNo

Use stable source fields in the IdP:

IdP source fieldSend as
Primary email / user principal emailemail
Given name / first namefirstName
Surname / family name / last namelastName

Map custom user fields

Step 3: Add custom field mappings

Use custom field mappings only for values that should update on every SSO login.

  1. In the SAML provider form, find Custom field mappings.
  2. Select Add mapping.
  3. Enter the SAML attribute 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. If the form says no custom user fields are defined, create or activate the custom fields first.

Step 4: Choose fields that should sync from the IdP

Good custom field candidates:

  • Department
  • Region
  • Employee type
  • Manager email
  • Cost center

Avoid mapping values that change often unless you want Built LMS to update that field every time the user signs in.

Verify success

The mapping is working when a pilot user signs in and:

  • The user lands in the expected Built LMS account.
  • The user's email matches the IdP email you intended to send.
  • First name and last name appear correctly, if sent.
  • Mapped custom fields update with the values from the SAML assertion.
  • The user's role and access are still correct after sign-in.

Troubleshooting

On this page