You don’t need to reinvent the wheel by creating your own user provisioning and management schema and APIs—just leverage the standards defined by SCIM.

Also, enabling SCIM for your app increases its potential user base by making it easy for enterprise admins to provision their users to it.

  1. Add a new application: Find and select a SCIM Provisioner with SAML (SCIM V2) and then add it.

2. Configure the application:

Enter the Playvox site tenant base URL and API keys in Base64 you created in your Playvox configuration.

SCIM 2.0 Base Url follow the structure:

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. Playvox offers a self-service API keys management process that allows you to generate the keys you need, modifying existing keys, and revoke keys to terminate access.

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

Example of API keys generated:

3. Enable provisioning: Enable provisioning in the provisioning tab and configure the behavior:

4. Select the roles: Then, the admin must select the roles which will affect the provisioning.

Note: In case the option "Required admin approval before this action is performed" is enabled, then the administrator must approve the provisioning in the Provisioning tab inside Onelogin platform

Troubleshooting Tips

  • Initial activation of OneLogin provisioning in Playvox requires reaching out Playvox Support, ( Please contact our team for questions during the configuration setup.

Note: When users are deactivated in OneLogin, 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, (

Last Edited: 24.08.20

Did this answer your question?