With Okta SCIM, Admins can automate their entire user's lifecycle in Dialpad — from creating accounts to profile updates, to account deletion.
In this article, we'll dive into Okta SCIM and show you step-by-step instructions on how to set up automatic provisioning.
Let's dive into the details.
If you haven't already, take a look at our help article on downloading Dialpad in Okta and setting up SSO via SAML.
Enable API access
To enable API access, you must have Super Admin or Company Admin access to your company's Dialpad account.
First, you'll need to configure and enable the API integration between Dialpad + Okta.
- Navigate to your Dialpad app in Okta
- Select Provisioning
- Navigate to API Integration
- Select Configure API Integration
- Check the box beside Enable API Integration
Once you've checked this option, you'll need to provide Okta with a new Dialpad API Token.
Once you've entered your API token, select Test API Credentials to ensure everything is syncing before selecting Save.
.png)
Provisioning to app (Dialpad)
Once your API is configured and synced, the next step is enabling the provisioning from Okta into Dialpad, like creating users, updating user info, or even deleting users.
Here's how:
- Select Edit
- Check the fields you want to enable (in our case, all)
- Select Save
.png)
Assign to users
Now that you've turned on provisioning, you'll need to assign your Dialpad app to your users. Here's how:
- Navigate to the Assignments tab
- Select Assign
- Select People
- Select Assign next to the individuals
You'll be prompted to review their username (it should be their email) and other profile details. If everything looks good, select Save and Go Back to return to the assignment page.
.png)
You can also assign groups to an app, if you've already created groups of users within Okta.
Once you've done this, your users will automatically be created in Dialpad, and a number will be auto-assigned based on the area code of the office you set up.
Okta attributes mapped to Dialpad
Let's dive into what Okta attributes are mapped to Dialpad.
Okta Attribute | Mapped Dialpad Field | Notes |
|---|---|---|
First Name | Name | First ame and Last Name combined |
Last Name | Name | First Name and Last Name combined |
Username | The user's handle@domain | |
department | Office | |
officeName | Office | Custom attribute (not available in Okta by default) |
countryCode | Country | |
preferredLanguage | Language | |
title | Job Title |
|
licenseType | License | Custom attribute (not available in Okta by default). Values can be any from the table below. |
License | Product |
|---|---|
dialpad_talk | Dialpad Connect |
dialpad_lite | Ai Voice(Lite) |
dialpad_support | Dialpad Support |
dialpad_sell | Dialpad Sell |
dialpad_tfb | Dialpad TfB Offer |
Frequently asked questions
When someone is removed from Dialpad via Okta, do they still appear in the Dialpad team list?
When you remove someone from the Dialpad app via Okta, the user will be suspended in Dialpad and no longer use a user license. While the user won't appear in your team list, you can still search for the user and verify their status is Suspended.
When you delete a user from Okta, the user is suspended from Dialpad, but they remain searchable.
Can I change a number or extension in OKTA SCIM?
No, these changes need to be made on our Admin portal. Check out our Number Assignment articles for more details.