Okta integration overview

Updated 8 days ago

Connect your Okta org to Simpplr to keep your people directory, audiences, and Launchpad in sync automatically. This article explains what you can do with the Okta integration and links to the setup steps for each task.

What you can sync from Okta

Capability	What it does	Usage	Article
Users & attributes	Syncs user profiles and selected profile fields from Okta into Simpplr.	Use to keep the people directory accurate - names, titles, departments, managers, and custom fields stay current without manual edits. Best when Okta is your source of truth for data.	Sync users and attributes with Okta
Groups	Creates and maintains Simpplr audiences from Okta groups.	Use to automate audience membership for content targeting and access - as people join or leave an Okta group, the matching Simpplr audience updates automatically.	Sync Okta groups to Simpplr audiences
Apps	Surfaces the Okta apps assigned to a user in Simpplr Launchpad.	Use to give employees one-click access to their work apps from inside Simpplr, reflecting each user's own Okta app assignments.	Sync Okta apps to Launchpad

How to connect

Simpplr connects to Okta using Okta Client OAuth. You'll create a dedicated API Services app in your Okta org, grant it read-only access to users, groups, and apps, and then authorize it in Simpplr. Simpplr handles authentication securely in the background, using scoped, automatically-rotating access, so there are no static tokens to manage, and the connection keeps working under stricter Okta org security policies.

Setting up takes a few minutes and moves between the Okta Admin Console and Simpplr. You'll need Super Admin access in Okta to complete it. See Connect Okta to Simpplr for step-by-step setup.

Before you begin

Okta SSO with Simpplr must already be set up. See Set up Okta SSO with Simpplr.
You must be a Super Admin in your Okta org to create the connection.
You must be an App Manager in Simpplr

How syncing works

Simpplr syncs from Okta on a daily schedule (overnight). You can also run a sync manually at any time, see "Run or schedule a sync."
Users are matched to existing Simpplr users by their Login Identifiers.

Note: This Okta integration is not the same as SCIM provisioning. They work in opposite directions and serve different needs.

Okta scheduled sync vs. SCIM provisioning

	Okta scheduled sync	SCIM provisioning
Direction	Simpplr pulls from Okta	Okta pushes to Simpplr
Timing	Scheduled (daily) or manual run	Real time, as changes happen
Triggered by	Simpplr	Okta
Setup	Okta Client OAuth	Configured separately via SCIM

Set up the integration

Connect Okta to Simpplr, choose a connection method and authenticate.
Sync users and attributes with Okta, select the fields to sync and run it.
(Optional) Sync Okta groups and Sync Okta apps to Launchpad.

Troubleshooting

Connection setup fails or shows a permission error

What happened: The Okta app is missing a required scope, or your Simpplr account doesn't have App Manager access.
What to do: Confirm the API Services app in Okta has read-only access to users, groups, and apps, and that you have App Manager access in Simpplr. Recreate the app or update permissions, then retry.

A user doesn't sync, or their profile data looks wrong

What happened: Simpplr matches users by Login Identifier. If this doesn't match between Okta and Simpplr, the user won't link correctly. If specific fields aren't updating, they may not be selected in the field mapping.
What to do: Check the Login Identifier matches in both systems. For field issues, confirm the field is mapped in Sync users and attributes with Okta, then run a manual sync.

An Okta group isn't creating or updating a Simpplr audience

What happened: The group hasn't been added to the sync configuration, or the change happened after the last sync.
What to do: Confirm the group is included in Sync Okta groups to Simpplr audiences, then run a manual sync.

Apps aren't showing (or aren't removed) in Launchpad

What happened: The apps sync hasn't run since the assignment changed in Okta.
What to do: Confirm Sync Okta apps to Launchpad is enabled and run a manual sync.

The overnight sync didn't run, or data seems stale

What happened: The Okta connection may have been disconnected or needs reauthorization.
What to do: Check the connection status in Simpplr's integration settings. Reauthorize if needed, then run a manual sync.

FAQs

Q: What's the difference between this integration and SCIM provisioning?
Ans: The Okta integration is a scheduled or on-demand sync that Simpplr pulls from Okta, mainly for keeping profile data, audiences, and Launchpad current. SCIM provisioning works in the opposite direction. Okta pushes changes to Simpplr in real time, typically for account creation, updates, and deactivation.

Q: Can I use both the Okta integration and SCIM provisioning at the same time?
Ans: Yes. They serve different purposes and are configured separately. SCIM handles real-time account lifecycle events, while this integration keeps directory data, audiences, and app access current.

Q: Does Simpplr write any data back to Okta?
Ans: No. The connection uses read-only access to users, groups, and apps in Okta. Simpplr only reads data; it doesn't make changes in your Okta org.

Q: How often does the sync run?
Ans: By default, it runs once daily, overnight. You can also trigger a sync manually at any time from the integration settings.

Q: Will the sync overwrite changes I made manually in Simpplr?
Ans: For any field selected in the field mapping, yes. Okta is treated as the source of truth for those fields, so manual edits to synced fields will be overwritten on the next sync. Fields not included in the mapping aren't affected.

Q: Do I need Okta SSO set up before configuring this integration?
Ans: Yes. Okta SSO with Simpplr must be set up first. The Okta integration builds on that connection.