Provision UserVoice access with Okta

Connect Okta to UserVoice with SAML sign-in and SCIM provisioning. Manage user access and, if you choose, map Okta groups to UserVoice teams.

Book a demo Read the setup guide

How it connects

Okta

User assignment and license mapping

SCIM v2

Provision or deactivate access

UserVoice

Access and team membership

SAML + SCIM

Sign-in and provisioning together

Groups

Optional push to UserVoice teams

Deactivate

Removes the license, blocks the user

Access managed where IT already works

Manage the access lifecycle

SCIM handles user attributes and license assignment. Deactivation removes the license and blocks the user. Their record and feedback stay in UserVoice.

Map groups to teams

Push Okta groups as UserVoice teams. SCIM then owns team assignments and overwrites manual changes.

Use the right app

Set up a SAML application with SCIM added, not the legacy UserVoice catalog app.

A good fit for

IT teams managing UserVoice access through Okta.

See how the UserVoice MCP works

Set up with your identity team

Read the setup guide

Coordinate both owners

A UserVoice owner and an Okta admin confirm the SAML application and access model.

Enable SCIM

Turn on SCIM under User Authentication, copy the token and configure the /api/scim_v2 endpoint with bearer authorization in Okta.

Map and test one user

Configure attributes, licenseType and optional groups. Test provisioning, changes and deactivation first.

Common questions

Does deactivation delete the user?

No. Deactivation removes the license and blocks the user, and their record and feedback stay in UserVoice. Deleting the user in Okta deletes them in UserVoice.