Skip to main content

How to Configure User Provisioning from Salesforce to Skillcast

Updated over a month ago

This article will walk you through configuring your Skillcast application to allow automated user provisioning via an external connection with Salesforce. Follow the steps below to ensure a smooth integration.

Before You Start

Speak to your Customer Success Manager (CSM) and Account Manager (AM) about your options and any costs associated with user provisioning. Discuss details such as which domains you want to use auto-provisioning on and what attributes you need to capture.

Your CSM will manage the Skillcast set-up part of the integration once all the necessary information is provided.

Preparing the Salesforce Instance

Skillcast LMS communicates with Salesforce using the built-in Salesforce REST API. To enable this, you need to allow Skillcast LMS access to the Salesforce API using a dedicated user account.

Steps to Prepare Salesforce:

  • Create a dedicated user account for Skillcast LMS

    • This user must be in a security group with access to manipulate custom objects and have permission to view all users in Salesforce.

    • You will need the Username, Password and Security Token for this user.

Generating a Security Token

  1. Log in to the Salesforce account.

  2. Click your profile avatar and choose ‘Settings’.

    Salesforce - profile avatar.png
  3. Select My Personal Information > Reset My Security Token.

    Salesforce - reset my token.png
  4. Check your email for the security token.

    Saleforce - toekn email.png
  • The Salesforce user must be an organisation member or have admin access to the repository where Skillcast users and training will be stored.

Preparing the Application

  • Create a dedicated Salesforce Connected App for Skillcast LMS

    • Log in to Salesforce as an Administrator.

    • Go to Setup.

      salesforce - set up.png
    • Navigate to PLATFORM TOOLS and select App Manager.

      salesforce - platform tools.png
    • Create a New Connected App.

      salesford - new connected app.png

Basic Information

  • Use clear naming conventions for transparency.

  • Use [email protected] as the contact email.

    Salesforce - basic information.png

API (Enable OAuth Settings)

  • Enable OAuth as Skillcast LMS will connect using OAuth.

    salesforce oAUTH consumer details.png

Custom Connected App Handler

  • Select the user created in the previous step as the “Run As” option for this Connected App.

    salesforce App Handler.png

Save the Connected App

Retrieving the Client ID and Client Secret

  • Navigate to PLATFORM TOOLS and select App Manager.

  • Find the Connected App and choose to View.

  • Under API (Enable OAuth Settings), select Manage Consumer Details.

  • Verify your identity if prompted.

    salesforce verify.png
  • Copy both the Consumer Key (Client ID) and Consumer Secret (Client Secret).

    salesforce key and secret.png
  • Add these to your File Exchange along with the attributes you wish to use in Skillcast.


What your CSM will do next

The following steps will be managed by your CSM.

Adding Salesforce Connection to Skillcast

  • Your CSM will use the Salesforce details to add a new external connection in Skillcast.

  • They will complete all required fields, including connection name, domain, features, username, password, client ID, client secret, and security token.

Setting Up User Provisioning on the Domain and Testing

  • Your CSM will ensure user attributes are mapped correctly.

  • They will add the connection to the relevant domain and test the integration before processing or scheduling the user provisioning

Limitations and Considerations

Note:


Conclusion

You have now learned how to prepare your Salesforce instance for automated user provisioning with Skillcast. Your CSM will handle the Skillcast configuration and testing. If you have any questions or need further assistance, please contact your Customer Success Manager by selecting Send us a message via the help icon on your portal, or by emailing [email protected].

Did this answer your question?