Set up a Pluralsight connector

C1 provides identity governance for Pluralsight. Integrate your Pluralsight account with C1 for unified visibility and governance over user access.

C1 provides identity governance for Pluralsight. Integrate your Pluralsight account with C1 for unified visibility and governance over users and team membership.

Capabilities

Resource	Sync	Provision
Users
Teams

Gather Pluralsight credentials

The Pluralsight connector is read-only. You need an account administrator to generate an API key.

1. Sign in to Pluralsight as an account administrator.

2. Open Integrations > API key management and generate an API key. Copy and store it — it is the connector’s api-key.

Configuration fields

Field	Required	Description
api-key	Yes	Pluralsight PaaS API key, sent as Authorization: Bearer <key> to https://paas-api.pluralsight.com/graphql.
base-url	Yes	Pluralsight API base URL (host only, no trailing slash). Set it to https://paas-api.pluralsight.com.

Synced resource types

• Users: the account’s Pluralsight users, mapped as C1 users. Each user carries id (stable external id), email, and name.
• Teams: Pluralsight teams, mapped as C1 groups. Each team exposes a member entitlement (and an admin entitlement for team managers). Team membership grants are derived from the authoritative teams connection on each user node.

Special notes

• The connector uses the Pluralsight GraphQL API: a single endpoint (POST /graphql) with cursor-based pagination (pageInfo.hasNextPage / endCursor).
• Pluralsight “roles” are skill / Role IQ development paths, not access roles; access is modeled exclusively through Teams.
• Team membership is read from each user’s teams connection (the authoritative relationship), not the legacy teamNames string array.
• The connector is read-only; it does not provision access.