Skip to main content
All CollectionsIntegrations
Configure User Provisioning with Okta
Configure User Provisioning with Okta

Follow these steps to integrate an Okta user directory with Seismic Learning

Joanna Brenneman avatar
Written by Joanna Brenneman
Updated over a week ago

In This Article

Before You Begin

You need four items to provision Seismic Learning users via Okta:

  1. The company's Okta URL.

    1. This should look like or

  2. A read-only Okta API token.

  3. A new user in the Okta directory with read-only access and a token for this user.

    1. This ensures Seismic Learning cannot accidentally make a change in the Okta environment or, if an Admin leaves, Learning won't need to update the script.

  4. An Okta group to sync to Seismic Learning.

    1. Learning can sync the entire Okta directory, but it's better to target a specific group in the Okta account.

Required User Profile Attributes

At a minimum, you must complete the following fields for each user:

  1. Name, first and last.

  2. Email address.

  3. Seismic Learning user role.

    1. Learner, creator, manager, or admin. If a role is not filled out, the user will default to a learner.

Other standard fields that can be included for each user are as follows:

  • Job title

  • Business unit

  • Department

  • Location

  • Manager name

Custom Attributes

For custom user fields to sync, Seismic Learning needs to know the variable name of the field in Okta. This can be found in the Okta Profile Editor.

Custom attributes could include the following:

  • Hire date

  • External user ID

  • Region

  • Division

Mapping Attributes

When setting up the standard Okta integration, mapping attributes need to be set up in the customer's Okta instance.

In Okta, navigate to Directory > Profile Editor, and locate the Seismic Learning app (if there are multiple Learning apps, this process has to be done for all of them). Select the profile editor button for the app. The Profile Editor page is where the attributes are mapped out.

After the desired attributes have been created in the app profile, these attributes need to be mapped to their corresponding fields in Okta by selecting the Map Attributes button.

Any other custom field needs to be provided by the customer with both the variableName and the Learning field name.

In the attribute mapping settings, there are two options at the top:

  1. Learning to Okta

  2. Okta to Learning

Select Okta to Learning. The sync must go from Okta to the application for it to work successfully.

On the left-hand side, the attributes are listed to be synced from Okta to the corresponding attribute in Seismic Learning. Between the attributes is an arrow. The user must select the arrow and select Apply mapping on user create and update. This is not intuitive but critical. The arrow should be green and pointing to the right. If the arrow is yellow then the attributes only sync for new users, and won't update previously synced users.

Select Save to finalize the setup.

Important Notes About Mapping Attributes

  1. When adding attributes, the Display Name of the attribute does not matter, but the Variable Name must match exactly.

  2. Dates in Seismic Learning are in ISO8601 format (YYYY/MM/DD). The Hire Date field must match this formatting.

  3. Groups won't automatically map during a standard integration. To recreate Okta groups in Learning, create a smart group according to some attribute that all group members share, e.g., manager name or department. Users will then be sorted according to the rules you set for each smart group.

How to Archive Users

Seismic Learning archives any users who are deactivated in Okta, and restores users when they are reactivated.

Sync Times

Synchronization occurs twice daily at 6:00 AM UTC and 3:00 PM UTC. These times cannot be customized.

If you're looking for real-time authorization, see this article about Okta SCIM.

Note: Standard Okta and Okta SCIM cannot co-exist. You must choose one or the other.

Questions? Contact the Support team at

Did this answer your question?