Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Adding Learner Attributes - Okta

Step-by-step instructions for sending Okta profile fields (like department or role) to Security Journey as learner attributes.

What are Learner Attributes?

You can map learner attributes (also called claims) from your identity provider to Security Journey. These attributes might include details like first name, last name, job title, job role, company, country, and more.

Mapping these attributes helps you:

  • Enrich learner profiles with accurate information from your system of record

  • Segment learners in reporting by using custom filters in Platform reports

  • Assign training more effectively by targeting specific groups within your organization (for example, by department, job role, or location)

To see the full list of supported claims, view our supported claims reference here.

Sure — here’s a short, Help Center–ready version.

Adding Learner Attributes (Okta)

You can send Okta user profile attributes to Security Journey as learner attributes using your SAML (SSO) integration (for example: Department, Role, or Location).

Prerequisites

  • Security Journey is already set up as an Okta SAML (SSO) app.

  • You have Okta admin access.

Add an Attribute

  1. In Okta, go to Directory → Profile Editor.

  2. Select your User Profile.

  3. Click Add Attribute, enter the details, then Save.

Map the Attribute to the SAML App

  1. Go to Applications → Applications and select the Security Journey app.

  2. Open Sign On → SAML Settings → Edit.

  3. Under Attribute Statements, add:

    • Name: the attribute name Security Journey should receive

    • Value: user.<attributeName> (example: user.department)

  4. Save.

Verify in Security Journey

Have a test learner sign in through Okta, then confirm the attribute appears on the learner’s profile in Security Journey.

Troubleshooting (Quick)

  • Missing attribute: confirm it’s mapped in SAML and the user has a value in Okta.

  • Not updated: attributes often refresh only after new authentication—you may need to have the learner sign in from an incognito session force a login.