ProServ Integrations. Customer will be provided with a variety of integrations to facilitate Customer’s use of Pluralsight. Customer must engage with Pluralsight to commence ProServ Integrations services within ninety (90) days of the Sales Order start date and such work shall be completed within sixty (60) days of agreed upon project kickoff date. Pluralsight will offer Customer support for Customer’s configured integrations for the initial Term of the underlying subscription Plan. In the event Customer desires; a) changes to the configured integrations after the initial Term, or b) configuration(s) of additional integrations, Customer must purchase additional ProServ Integrations services.

(a) Single Sign-On (SSO). Pluralsight supports SSO using SAML 2.0 as the standard. SSO is a configuration between Customer and Pluralsight (or Customer’s LMS and Pluralsight) that allows Users to provision a Pluralsight log-in and/or login to the Pluralsight Platform without the need for Pluralsight-specific credentials. Customers are responsible for the IdP side of such connection. SAML spec is followed universally, both SP and IdP initiated linking and deep linking are supported. Customer may also choose self-provisioning, which does not use SAML JIT.

(b) Auto SSO. Customer may be given the ability to have Pluralsight build issuance criteria and automated channel, team and plan mapping, but agrees that any such attributes delivered across the SSO configuration are Customer’s responsibility; and as such, Customer disclaims any and all liability associated with alignment to any such attributes.

(c) Data Export. Pluralsight offers additional data feeds of usage information beyond Pluralsight’s standard dashboard that can be exported to a .CSV or .TXT file (said process referred herein as “Data Export”). Delimiter options include pipe, tab, space, and comma, and while the file naming conventions may be customizable, Pluralsight provides no guarantee of data delivery. Data Export can be enabled to trigger one-time or on a daily, weekly, or monthly recurring basis via Customer’s FTP, or SFTP (hereinafter “Data Export Instruments”). Pluralsight is not responsible to provide or support Customer’s Data Export Instruments and further agrees that delivery times of such Data Exports may vary. Delivery of Data Exports has the following limitations; must not require “SSH Key Auth”, PGP Encryption, FTP-SSL-Delivery, or POST/PUT to an API endpoint.