Articles in this section

Manage Users with Google Workspace SCIM

With Google SCIM, Dialpad Administrators can automate their users' entire lifecycle in Dialpad — from creating accounts to profile updates to even account deactivation.

Let's dive into the details. 

Who can use this

Google Workspace + SCIM integrations are available to eligible Dialpad Sell, Dialpad Support, and Dialpad Connect users. Refer to our to see if you have access to this feature. If you have questions about your plan, reach out to your Customer Success Manager or Dialpad Customer Care.

Set up user provisioning 

First things first, you’ll need to select and add the Dialpad app from the G Suite SAML catalog with the “Provisioning supported” field enabled.

Once that's done, you can start laying the groundwork for user provisioning. Once completed, automatically provisioned users will be assigned the same area code as their Office. 

If you’d rather avoid this, you can either manually provision the user or follow the steps outlined in Step 4.

From the Google Admin Console:

  1. Navigate to Web and mobile apps
  2. Select the Dialpad app
    Screenshot of the Google Admin Console under 'Web and mobile apps', listing installed applications including Dialpad, Dialpad Sandbox SCIM, and DialpadSandbox with their respective platform, authentication, and user access statuses.
  3. Navigate to the Autoprovisioning section 
  4. Select Configure Autoprovisioning

 

Step 1: App Authorization

Before provisioning users, you need to authorize Google to do so. 

Head to your Dialpad Admin Settings.

  1. Select My Company
  2. Navigate to Authentication
  3. Select API Keys
  4. Select Add key

    Screenshot of the Dialpad Admin Settings API Keys page, featuring an orange arrow pointing to the highlighted '+ Add key' button on the top right.
  5. Name your key, then select Save
  6. Copy the API key
  7. Return to the Google Admin page and paste the key into the field in App authorization section
    Screenshot of the 'Set up autoprovisioning for Dialpad' workflow in Google Admin Console, showing Step 1: App authorization with an API key pasted into the 'Access token' field.
  8. Select Save

Step 2: Attribute Mapping

Next, it is time to map Google Directory attributes to the corresponding Dialpad app user attributes. 

Any attributes with a * must be mapped.

Screenshot of the attribute mapping interface displaying a side-by-side list of dropdown fields connecting Google Directory attributes to Dialpad App attributes, with a blue 'Continue' button highlighted in the bottom right.

You can also map the user's assigned Dialpad office by mapping the relevant field from Google Directory to the department attribute under the Dialpad app.

Once you've set the attributes, select Continue.

Step 3: Configure Group-Based Provisioning (Optional)

Group-based provisioning is optional and involves restricting provisioning to the specific groups you identify. If you're not restricting provisioning to a specific groups of team members, leave this section empty.

Enter the desired groups in the search bar, then select Continue. 

Screenshot of the Provisioning scope interface displaying an empty 'Search groups' search bar and a blue 'Continue' button in the bottom right corner.

Step 4: Deprovisioning settings

Deprovisioning settings determine how user deletion or removal from the Dialpad app in Google will affect the user’s state (active/suspended). 

Note

If you are testing the provisioning steps before activating them for your team, please deconfigure your de-provisioning steps. (uncheck all of the boxes shown below)

Screenshot of deprovisioning options showing configurable checkboxes for account suspension and deletion timeframe triggers, with a blue 'Finish' button highlighted in the bottom right corner.

When the above checkboxes are selected, Google will sync with the Dialpad office and see that there are users in Dialpad that are not in the test group you created, then suspend the Dialpad users. You will need to uncheck all of those boxes if you are testing provisioning and not de-provisioning.

Select Finish to complete auto provisioning configuration.

Note
If you do not have any Dialpad licenses on your account, one will automatically be added once you invite a user.

Activate provisioning

Now that you've finished setting up your user provisioning, the last steps are to turn Dialpad on for your users and activate automatic provisioning.

Turn on Dialpad for users (optional)

To turn on Dialpad for all (or some of) your users head to your Google Admin portal:

  1. Select Web and Mobile apps
  2. Select Dialpad
  3. Select User Access and choose one of the three available options:
    • ON for everyone: Turns on service for all users
    • OFF: Turns off service for all users
    • ON for some organizations: Changes settings for only some users

      Screenshot of the Dialpad Service Status page displaying radio buttons to toggle service access on or off, alongside an organizational unit selection sidebar on the left and 'Cancel' and 'Save' buttons in the bottom right corner.
Note
If the Dialpad app was already turned on while setting up SAML authentication, this section can be skipped.

Activate auto provisioning

Last but not least, it's time to activate auto provisioning. 

From the User Provisioning tab:

  1. Navigate to Activate Provisioning
  2. Slide the toggle on

    Screenshot of the Autoprovisioning settings dashboard displaying sync activity metrics, featuring an orange box and arrow highlighting an inactive toggle switch.
  3. Confirm the provisioning tasks are complete, then select Turn On

After a few moments, auto-provisioning will begin, and you'll see a green checkmark under Autoprovisioning.  

Screenshot of the active Autoprovisioning dashboard, featuring an orange box and arrow highlighting the 'Syncing active' status with a green checkmark next to a 'view sync log' link.

From the Autoprovisioning section, you can see how many users were created, suspended, or deleted, as well as download the sync log. 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.