Skip to main content
This guide connects Okta to Reelevant, so Okta creates, updates, and deactivates Reelevant accounts for you. Read Automatic User Provisioning first — it explains the settings you choose here.

​
Before You Begin

  • Turn provisioning on in Reelevant, then copy the base address and generate an access key.
  • You need administrator rights in Okta.
  • Create in Reelevant the roles you want Okta users to receive.

​
Step 1 — Create The Application In Okta

1

Open the applications list

In the Okta admin console, go to Applications and click Create App Integration.
2

Pick the integration type

Choose SWA or SAML 2.0 depending on how your people log in, then give the application a name such as “Reelevant”.
3

Assign people

On the Assignments tab, assign the groups or the individuals who should have a Reelevant account.
Logging in is handled by single sign-on, and provisioning is configured separately below. Assigning someone in Okta is what creates their Reelevant account.

​
Step 2 — Connect Provisioning

1

Open the Provisioning tab

Open the application, go to Provisioning, then open the integration settings so you can enter the Reelevant values.
2

Paste the Reelevant values

3

Test the connection

Run the credentials test. Okta checks what Reelevant supports and confirms the connection.If the test fails, check that provisioning is switched on in Reelevant and that the access key has not been revoked.
4

Choose the actions to enable

Save, then click Edit next to Provisioning to App and enable:
  • Create Users
  • Update User Attributes
  • Deactivate Users

​
Step 3 — Map The Attributes

Open Provisioning → To App → Attribute Mappings. Keep these mappings, and remove anything else — extra attributes are ignored.
Email addresses and user names always match: if Okta sends both and they differ, the user name wins.

​
Step 4 — Push Groups

Only do this if you kept group synchronisation on in Reelevant.
1

Open Push Groups

In the application, open the Push Groups tab.
2

Add the groups to push

Click Push Groups, then pick the Okta groups that should become Reelevant Teams.
3

Save and let Okta push

Each pushed group creates a Team of the same name, and its members join that Team.
If you chose from groups to decide roles, use here exactly the group names you listed in the Reelevant role mapping. Names are compared ignoring upper and lower case.

​
Step 5 — Test With One Person

1

Assign a test person

Assign one test person to the application in Okta.
2

Check the account in Reelevant

Open the Users page. The account appears with the expected role and Teams.The person has no password: they log in through single sign-on. No invitation email is sent.
3

Deactivate the test person

Deactivate them in Okta, or remove their assignment to the application.
4

Check the result

In Reelevant, the account is now deactivated or deleted, following the choice you made in the provisioning settings.Open sessions are closed immediately, so the person loses access straight away.
5

Read the audit log

The audit log shows each of these events, with the exact time and outcome.

​
If Something Does Not Work

​
What’s Next?

Provisioning settings

Review roles, Teams, and what happens when someone leaves.

Audit log

Check what was created, changed, or deactivated.

Microsoft Entra ID

The same setup with Microsoft Entra ID.

Users

See provisioned people and their status.