Configure Salesforce auto-provisioning

We recommend you try out the auto-provisioning feature in the Salesforce Sandbox before you implement it in your Salesforce production environment.

As an administrator, once you've set up SSO, your next step is to set up automated user provisioning to authorize, create, modify, or delete your users' identity once in G Suite, and have the changes to that identity reflected in Salesforce.

Set up auto-provisioning for the Salesforce application
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Open the Salesforce application.
  4. In the Auto-provisioning section, click Configure auto-provisioning.
  5. Click Authorize.

    Salesforce opens in the same tab. If you haven't signed into your Salesforce administrator account before clicking Authorize, you're prompted to sign in. If you can't access your Salesforce application, click Re-authorize app to be prompted to sign in.

    Important: You might have to reauthorize if the admin password for Salesforce has changed. Changing the admin password will cause the original authorization to be revoked.

  6. Edit the Endpoint URL, replacing {domain} with the domain associated with your Salesforce account.
  7. Click Continue.
  8. Verify that all mandatory Salesforce attributes (those marked with an *) are mapped to Google Cloud Directory attributes. If not, click the Down arrow "" and map to the appropriate attribute.
  9. Click Continue.
  10.  (Optional) Restrict provisioning to specific groups:
    1. Enter all or part of a group name in the Search groups field.
      A list of available groups appears. Select a group to add it and open a new search field.
    2. If necessary, add more groups and choose a scope. 
    3. To remove any group you added, click "" next to it.
  11. Once you’re done, click Continue.
  12. Choose how long deprovisioning actions should be delayed before taking effect. You can set the time to: within 24 hours or after one, 7, or 21 days. Select at least one of these options:
    • When an app is turned off for the user, suspend their account, soft delete their account, or both,  after [number of days].
    • When a user is suspended on Google, suspend their account, soft delete their account, or both,  after [number of days].
    • When a user is deleted from Google, suspend their account, soft delete their account, or both,  after [number of days].
    • A suspended account is temporarily unavailable until it's restored. A soft deleted account can be restored without data loss up to 7 days after deletion.

    Tip: Always set more time before hard deleting a user's account than for suspending a user's account.

  13. Click Finish.
  14. In the Auto-provisioning section, click the activation slider.

    Note: The activation slider is disabled if Salesforce isn’t turned on for any users. Click User access and turn the app on to enable the slider.

  15. In the confirmation dialog box, click Turn on.
Display auto-provisioning

Once provisioning is on, Google starts collecting usage information. You'll see the usage information in the Auto-provisioning section. There won't be any numbers next to the event names until you enable provisioning.

The following event names provide the usage information for the last 30 days:

  • Users created
  • Users suspended
  • Users deleted
  • Failures

For more information, see Monitor automated user provisioning.

Edit provisioning scope

You may want to restrict the scope of provisioning to members of groups you define. 

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Open the Salesforce application.
  4. Click the Auto-provisioning section to open the settings page.
  5. Under Provisioning scope, click Edit.
  6. Enter all or part of a group name in the Search groups field. A list of available groups appears.
    1. Select a group to add it and open a new search field.
    2. If necessary, add more groups and choose a scope. 
    3. To remove any group you added, click "" next to it.
  7. Once you’re done, click Update.

The next time you edit provisioning scope, the groups you added appear in the Provisioning scope window. If you turned on the Salesforce application for a set of organizational units, the provisioning scope is restricted to those users in the added groups who are also members of those organizations.

Deactivate auto-provisioning

To disable auto-provisioning for the Salesforce application without losing all the configuration information:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Open the Salesforce application.
  4. Do one of the following:
    • In the Auto-provisioning section, click the activation slider.
    • Click the Auto-provisioning section to open the settings page, then click Statusand thenTurn off.
  5. In the confirmation dialog box, click Turn off
Define deprovisioning timeframes

To define how long deprovisioning actions should be delayed before taking effect:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Open the Salesforce application.
  4. Click the Auto-provisioning section to open the settings page.
  5. Under Deprovisioning, click Edit.
  6. Choose how long deprovisioning actions should be delayed before taking effect. You can set the time to: within 24 hours or after one, 7, or 21 days. Select at least one of these options:
    • When an app is turned off for the user, suspend their account, soft delete their account, or both,  after [number of days].
    • When a user is suspended on Google, suspend their account, soft delete their account, or both,  after [number of days].
    • When a user is deleted from Google, suspend their account, soft delete their account, or both,  after [number of days].
    • A suspended account is temporarily unavailable until it's restored. A soft deleted account can be restored without data loss up to 7 days after deletion.

    Tip: Always set more time before hard deleting a user's account than for suspending a user's account.

  7. Click Update to save your edited deprovisioning configuration.
Remove auto-provisioning

To disable auto-provisioning for the Salesforce application and remove all the configuration information:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Open the Salesforce application.
  4. Click the Auto-provisioning section to open the settings page.
  5. Under Delete configuration, click Delete.
  6. Click Delete to both deactivate auto-provisioning and remove all the configuration information.
    Existing users on Salesforce will not be deprovisioned.
Important: If automatic provisioning stops and you need to reauthorize the application

If the admin password for Salesforce has changed, automatic provisioning will stop working. In this case, the original authorization is revoked by Salesforce, and you must reauthorize automatic provisioning.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.

  3. Click the Salesforce application.
  4. Click the Auto-provisioning section to open the settings page.
  5. Under App authorization, click Reauthorize.
  6. Click Re-authorize.

    If you haven't recently signed in to Salesforce, you may need to sign in during reauthorization.

After reauthorization completes, you're returned to the Auto-provisioning settings page in the Admin console.

Note: Your third-party application might revoke authorization for reasons other than the admin password changing. These reasons can include account inactivity, for example. Check with the documentation for the third-party application for scenarios in which authorization can be revoked.

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue