Life is complicated, and the only constant is change. As a user’s lifecycle within your company shifts, you may need to edit their access to connected apps. Manually editing which user is connected to which app at any given moment takes precious time away from your priorities, but user provisioning (and deprovisioning) allows you to centralize app management to reflect the ever-changing lifecycle of your users.

If Okta is your IdP, you’re in the right place! We’ll help you set up User Provisioning with Playvox.

What is User Provisioning?

User provisioning or account provisioning technology creates, modifies, disables and deletes user accounts and their profiles across IT infrastructure and business applications. Provisioning tools use approaches such as cloning, roles and business rules so that businesses can automate onboarding, offboarding and other administration workforce processes...” - Gartner Glossary

Before we get started, let’s go through our supported features as well as some requirements.

Supported Features

  • Push New Users: New users created through OKTA will also be created in Playvox.

  • Push Profile Updates: Updates made to the user's profile through OKTA will be pushed to Playvox.

  • Push User Deactivation: Deactivating the user or disabling the user's access to the application through OKTA will deactivate the user in Playvox.

Note: Deactivating a user in Playvox will not delete the user’s data or account. It will simply prevent the user from signing in or completing new evaluations.

  • Reactivate Users: User accounts may be reactivated.


  1. Make sure your API Keys are enabled.

  • Go to Settings > Roles Management in Playvox.

  • Select Essentials from the Admin or Super Admin role.

  • Scroll down to API Keys Permissions and select Generate API Keys.

Note: If you don't see this as an option on your settings, please reach out to your account administrator to request access visibility.

Check out this article if you’d like to Assign API Key Management Permissions to Specific Roles.

2. You’ll also want to make sure that Okta SSO is set up and ready to go on the site

before setting up User Provisioning with Okta.

Important: If you don’t see the option to Allow SAML sign on for everyone under Settings>Community>Security, please contact Playvox Support at They will need to set up the initial activation of Okta provisioning.

Generate your API keys

If you have a subscription that includes API access, you can call the API on-demand using the appropriate credentials. These exist as User ID and API Key pairs.

  1. Click here to learn how to generate the keys you need, modifying existing keys, and revoke keys to terminate access.

Note: Please see Playvox Developers for full documentation on the Playvox API.

2. Once generated, you’ll see the Name of the Key, the User ID, the API Key, and a

Base64 Key (if required).

3. Keep this window open, and sign into Okta for the next step.

Enable SCIM API integration in Okta

After generating your API Keys in Playvox, you’ll need to configure provisioning in Okta.

  1. Log in to Okta and search for the Playvox application.

2. Click Add.

3. A new page will open. Click on the Provisioning tab.

Click on Provisioning

4. Then click on Configure API Integration.

Click on Configure API Integration

5. Check Enable API integration.

Check Enable API integration

6. Next, fill in your Base URL making sure you use your subdomain where indicated

in the example below.

SCIM 2.0 Base Url follows this structure:


7. Fill in your API Token with the BASE64 Key from the Playvox API key you

generated earlier.

Fill in your API Token with the BASE64 Key from the Playvox API key you generated earlier.

Copy from here:

Paste to here:

8. Click Test API Credentials.

Click Test API Credentials

9. A confirmation message will appear if the test was successful.

A confirmation message will appear if the test was successful

10. Then click Save.

Click Save.

11. A new window will appear. Make sure you're on the To App tab.

12. You're ready to enable provisioning! Click Edit.

13. Check Enable for the features you'd like to utilize.

Check Enable for the features you'd like to utilize.

14. When you're finished, click Save.

Hoorah! You’ve successfully set up User Provisioning using SCIM with Okta. Life just got a whole lot easier, and we’re happy for you!

Remember: When users are deactivated in Okta, they will be deactivated in Playvox. Users will not be able to login to the application, but their data will remain available as an ‘inactive user’. To permanently delete user data, contact Playvox Support at

Did this answer your question?