evident
FeaturesQuestionnairesRFPsThird-party riskPricing
Log inBook a demo
  1. Home
  2. Integrations
  3. Okta single sign-on and SCIM provisioning for Evident
Identity and access

Okta single sign-on and SCIM provisioning for Evident

Add Evident from the Okta Integration Network, sign in with SAML single sign-on, and add, update and deactivate Evident users from Okta with SCIM.

NNate LeeCo-Founder, CEOPublishedNovember 15, 2026

Integration

Okta

Category
Identity and access
Available on
Plans with SAML single sign-on

Add Evident from the Okta Integration Network and your people sign in to Evident with Okta. Turn on SCIM provisioning and Okta adds, updates and removes them in Evident for you, so nobody keeps a second list of who has access.

If you can't find Evident in the Okta catalog yet, follow the custom app steps on Settings → Security & sign-in in Evident instead. They set up the same connection by hand.

What does the Okta integration do?

It lets your team sign in to Evident through Okta, and it keeps Evident's member list and teams in step with the people and groups in Okta.

  • Single sign-on (SAML 2.0). People sign in to Evident with their Okta account. Sign-in starts from Evident (SP-initiated).
  • Just-in-time accounts. Someone with an email at your verified domain who signs in for the first time gets an Evident account as a member.
  • Create users. People you assign to the Evident app in Okta are added to Evident.
  • Update user attributes. Name, username and email changes in Okta reach Evident.
  • Deactivate users. Deactivating someone in Okta, or removing them from the app, turns off their Evident access. Their questionnaire history stays.
  • Push groups. Groups you push from Okta appear in Evident, where an admin links each one to a team. The team's members then follow the group.

Evident doesn't support sign-in started from the Okta dashboard (IdP-initiated) or single logout.

What do I need before I start?

You need an Evident admin account on a plan with SAML single sign-on, an Okta admin who can add apps, and access to your domain's DNS records.

  • An Evident admin account, on a plan that includes SAML single sign-on. If you don't see Settings → Security & sign-in, or it asks you to upgrade, contact us to turn single sign-on on for your organization.
  • An Okta administrator with the super admin role, or the app admin and org admin roles.
  • Someone who can add a DNS TXT record for your email domain.

How do I set up single sign-on?

Verify your email domain in Evident, add Evident from the Okta catalog with your organization ID, then paste Okta's metadata URL into Evident.

  1. 1

    Verify your email domain in Evident

    In Evident, open Settings, then Security & sign-in. Add your email domain and create the DNS TXT record it shows. Evident only signs in people whose email is at a verified domain.

  2. 2

    Copy your Evident organization ID

    On the same page, find the SP entity ID. It ends in /sso/ followed by your organization ID. Copy that last part.

  3. 3

    Add Evident from the Okta catalog

    In the Okta Admin Console, go to Applications, then Applications, and select Browse App Catalog. Search for Evident and select Add Integration. Paste your organization ID into Evident organization ID and finish the General Settings.

  4. 4

    Use the same username for sign-in and SCIM

    On the app's Sign On tab, set Application username format to the Okta user ID (Custom, user.getInternalProperty("id")). Evident uses it as the SAML NameID and the SCIM userName, and it never changes when someone's email does.

  5. 5

    Give Okta's metadata to Evident

    On the Sign On tab, copy the Metadata URL. In Evident, paste it into the identity provider metadata box on Settings, then Security & sign-in, and save.

  6. 6

    Assign people and test

    Assign the Evident app to one broad group, such as everyone who uses Evident. Then use Test sign-in in Evident, or sign in at app.evident.security/login with a work email.

Okta sends the person's email in the SAML response; Evident needs it to match the person to their account. Okta also sends their groups, so teams can follow groups even without SCIM.

How do I turn on SCIM provisioning?

Create a SCIM token in Evident, paste it into the app's Provisioning tab in Okta, then turn on creating, updating and deactivating users.

  1. 1

    Create a SCIM token in Evident

    In Evident, open Settings, then Security & sign-in, and turn on SCIM. Copy the token. Evident shows it only once.

  2. 2

    Connect Okta to Evident

    In Okta, open the Evident app, then the Provisioning tab, and select Configure API Integration. Turn on Enable API integration, paste the token, select Test API Credentials, then Save.

  3. 3

    Choose what Okta changes in Evident

    Under Provisioning, then To App, select Edit and turn on Create Users, Update User Attributes and Deactivate Users. Save.

  4. 4

    Send your people

    Assign the app to the people or the broad group who should use Evident. Anyone assigned before Create Users was on needs Provision User on the Assignments tab, or remove and re-assign them.

  5. 5

    Push groups for teams

    On the Push Groups tab, push the groups that match your Evident teams. In Evident, link each pushed group to a team on Settings, then Security & sign-in.

Keep the group that gives access to Evident separate from the groups you push for teams. If one group does both, removing someone from it turns off their Evident access instead of only taking them off the team.

What happens when people change in Okta?

Okta sends each change to Evident as it happens. Suspending someone does nothing in Evident; deactivating or unassigning them turns off access.

| In Okta | In Evident | | --- | --- | | Assign the app | The person is added as a member, or linked to their existing account by email | | Change name, username or email | The change is saved; a new email must be at a verified domain | | Remove from a pushed group | They leave the linked team | | Unassign the app or deactivate | Their access is turned off; their history stays | | Re-assign or reactivate | Their access comes back. Their role is the one they had before, or the role of a linked team they belong to | | Suspend | Nothing. Okta stops their sign-in, but an open Evident session continues |

How do I fix a failed sign-in or push?

Most problems come from an unverified domain, a value pasted in the wrong field, or people assigned before provisioning was turned on.

  • "The email's domain is not verified by this organization." Verify that domain in Evident, then retry the push in Okta.
  • Sign-in fails right after setup. Check that the organization ID in the app's General tab matches the end of the SP entity ID in Evident, and that Evident has Okta's current metadata.
  • "User was assigned this application before Provisioning was enabled." Select Provision User for that person, or remove and re-assign them.
  • A push was refused. The reason is under Dashboard, then Tasks, in Okta. Evident shows the last SCIM error on Settings, then Security & sign-in.
  • A pushed group name clashes. Evident names the group in the error. Rename one of the two groups, or link the existing one.

Using Microsoft Entra ID as well? See Microsoft Entra ID single sign-on for Evident.

How do I get help?

Email the Evident support team with your organization name and what you were doing, and we'll help you finish the setup or fix the error.

Write to [email protected]. For how Evident protects your data, see security at Evident. For the tools Evident connects to, see all integrations.

Let IT manage who uses Evident

Connect Okta once. People sign in with their work account, and joiners and leavers follow your directory.

See pricing
N
Nate Lee

Co-Founder, CEO

Former CISO. A decade of filling these out by hand, across SIG, CAIQ, custom spreadsheets, and every vendor portal that's ever existed.

LinkedIn
evident

Product

FeaturesPricingWhat’s newSlackMCPFor sales teams

Company

AboutBlogGlossary

Legal

SecurityPrivacyTermsDPAResponsible disclosure