Workday Connector

The Workday Connector allows you to make your Pluralsight team structure align with your Workday org structure. This will allow both learners and leaders to leverage in-app learning analytics, skill inventory, and skill progression over time and by team. This connector does NOT include sending content progress or the content catalog information back to Workday.

Team Structure Import Functionality

  • One way, Workday to Pluralsight, team structure synchronization ( ie teams, team members, managers).
    • Workday users are matched to Pluralsight users by primary email and/or SSO ID.
    • Add a licensed user to team A.
    • Move a licensed user from team A to team B.
    • Invite a manager to team A via email. (If the manager already exists on that team they will not be invited.)
    • Add/remove a manager for team A. (A manager is added as a non-licensed user.)
    • Add/remove teams in Pluralsight. (Teams without licensed users won’t be added.)
    • Edit team names and add/remove/change the parent team.
  • Frequency of org structure sync from Workday to Pluralsight is dependent on your needs but we recommend at least weekly.

What's not included in the Team Structure Import

  • Sending any information back to Workday from Pluralsight. Including:
    • Content Progress
    • Content Library
  • New licensed user invitations: No new Pluralsight user licenses will be assigned. (Managers created by connector do not consume a license).
  • Deprovisioning of user licenses upon termination in Workday. Please view the license Deprovision integration for this functionality.

Workday Configuration using the outbound EIB

More detailed instructions for setting up the EIB within Workday can be found on the Workday EIB page.

Why we recommend the Outbound EIB Integration as Pluralsight's preferred method

  • You are able to use the existing Pluralsight API token for authentication rather than having to manage a separate set of credentials.
  • The team sync will be triggered whenever you upload files to us, so it puts you in control of the scheduling.
  • Security considerations
    • HTTP/SSL uses SSL (a secure channel between two machines or devices operating over the internet) and is considered secure.
    • HTTP/SSL uses the TLS protocol which comes with a bit more complexity (public trust infrastructure) but with that complexity comes the benefit that you can rely on our trusted TLS cert to verify we are who we say we are.