Getting Started with the Team Structure Connector

In this article:

• Overview
• Features
• Recommended steps
• Recommended testing strategies

Overview

The Team Structure Connector is a tool designed to align your Pluralsight team structure with your organizational hierarchy. This will allow both learners and leaders to leverage in-app learning analytics, skill inventory, and skill progression over time and by team. Note: The Team Structure Connector can connect with Workday HRIS systems, but does not include sending content progress or content catalog information back to Workday.

Features

The Team Structure Connector is a synchronizes your team structure (i.e. teams, team members, team managers) with the Pluralsight system. This is a one-way connector that syncs your existing hierarchy in the Pluralsight ecosystem.

The Team Structure Connector can

• Add licensed users to a team
• Move a licensed user from team A to team B
• Invite a manager to a team (they will not be invited if they are already a manager of that team)
• Add or remove a manager from a team
• Add or remove a team
• Edit team names
• Add, remove, or change a parent team automatically within the Pluralsight system without the need for manual action.

Frequency of team structure sync into Pluralsight is dependent on your needs but we recommend at least weekly.

Recommended Steps

1. Familiarize yourself with the authentication requirements on the Authentication page.

2. Follow the setup instructions:

   • General setup: Navigate to the Team Structure Connector Setup.
   • Workday-specific setup: For Workday users, refer to the Workday EIB Setup page for guidance on setting up your Workday EIB.

3. Test your setup:

   • Follow the recommended testing strategy below to verify that your setup is functioning correctly.

4. Review results and troubleshoot errors:

   • General review: Check the results on the Team Structure Connector Results page and refer to the Troubleshooting section there for any issues encountered.

Recommended testing strategies

1. Initial Dry Run
   • Action: Run the sync with the dryRun URL parameter set to true. Note: This is the default behavior if you do not set the URL parameter.
   • Optional: Consider using strict mode to stop the process if there are any errors. Refer to “Turning On Strict Mode (ExitOnError)” for details.
2. Review Results
   • Check Errors/Warnings: Go to the Results page to review any errors or warnings from file validation.
   • Review Operations:
     • Is the total number of users/teams created within your estimated range?
     • Is the total number of managers invited within your estimated range?
     • If numbers aren’t as expected:
       • Click the View All button next to the opperation to see all instances of that operation.
       • Click Download Log below the table to see in-depth results and diagnose issues.
3. Prepare for Full Sync
   • Before Turning Off dryRun:
     • If there are manually created teams you wish to retain, use the rootTeamIds URL parameter to specify which teams to sync, as mentioned in the “Syncing Only a Part of Your Organization/Retain Manually Created Teams” section.
     • Note: Team names must be unique in Pluralsight. If a team name in teams.csv matches an existing name, the existing team will be moved as per the new hierarchy.
     • If you do not want manager invitation emails during testing, review the “Turning Off Manager Invites” section.
4. Full Sync Testing of a single team
   • Action: Run the sync with dryRun URL parameter set to false.
   • Verification:
     • Send info for 1 team/manager to verify in-app experience. You can do this by:
       • Using the id of the team as the rootTeamIds URL parameter.
       • Reducing the information in the files you send to only include the 1 team in the teams file and the members of that team in the users file.
5. Scaled Testing Approach
   • Action: Once a single team structure looks good, scale to 2-3 levels of teams to ensure correct data mapping via users and teams files.
   • Verification: Check the results on the Pluralsight platform.
6. Final Sync
   • Action: Send the entire data set for final sync.
   • Review Results: Check the outcomes of the sync process.
7. Automated Sync
   • Action: Consider turning on sendManagerInvites for automatic manager invitations (Note: Manager invites don't consume licenses).
   • Frequency: Choose a sync frequency based on your needs; most customers opt for daily or weekly automated syncs.