Pylon

Syncs Pylon users, teams (with memberships), and user roles, and provisions team membership via the Pylon REST API.

Pylon

The Pylon connector syncs identities and access from Pylon and provisions team membership through the Pylon REST API.

Synced resources

Resource	Capabilities
User	Sync
Team	Sync, team membership provisioning
Role	Sync (read-only — manage in Pylon)

Team resources expose a member grant for every user listed on the team. Role resources expose an assigned grant for every user who has that role; role grants are read-only because the Pylon API only supports replacing a user’s single role_id rather than add/remove semantics.

Configuration

Field	Required	Description
api-key	yes	Pylon API token. Only Admin users can mint these in Pylon under Settings > API Tokens. Sent as the Authorization: Bearer <token> header on every request.

Required permissions

The API token must belong to an Admin user. Pylon’s API requires admin scope for the endpoints the connector reads (/users, /teams, /user-roles, /me) and for the team membership updates used during provisioning (PATCH /teams/{id}).