Coupa Contingent Workforce

Configuring the Coupa Contingent Workforce integration for Veza Lifecycle Management.

Overview

The Veza integration for Coupa Contingent Workforce (CCW) enables automated identity synchronization as a source of truth for contingent worker lifecycle management. Coupa CCW serves as an authoritative source for contingent worker information that can be synchronized with other systems in your environment.

This document includes steps to enable the Coupa CCW integration for use in Lifecycle Management, along with supported actions and notes. See Supported Actions for more details.

Enabling Lifecycle Management for Coupa CCW

Prerequisites

  1. You will need administrative access in Veza to configure the integration and Customer Integration Admin privileges in Coupa CCW.

  2. Ensure you have an existing Coupa CCW integration in Veza or add a new one for use with Lifecycle Management.

  3. Verify your Coupa CCW integration has completed at least one successful extraction

  4. The Coupa CCW integration will need the required API scope:

    • ccw.contingent_workers - For accessing contingent worker data

Configuration Steps

To enable the integration:

  1. In Veza, go to the Integrations overview

  2. Search for or create a Coupa CCW integration

  3. Check the box to Enable usage for Lifecycle Management

Configure the extraction schedule to ensure your Coupa CCW data remains current:

  1. Go to Veza Administration > System Settings

  2. In Pipeline > Extraction Interval, set your preferred interval

  3. Optionally, set a custom override for Coupa CCW in the Active Overrides section

To verify the health of the Lifecycle Management data source:

  1. Use the main Veza navigation menu to open the Lifecycle Management > Integrations page or the Veza Integrations overview

  2. Search for the integration and click the name to view details

  3. In the Properties panel, click the magnifying glass icon under Lifecycle Management Enabled

Supported Actions

Coupa CCW can serve as a source for identity information in Lifecycle Management Policies. Contingent worker identity details are synchronized from Coupa CCW with changes propagated to connected target systems.

Important: Coupa CCW is a source-only integration for Lifecycle Management. It provides authoritative identity information but cannot be used as a provisioning target.

The integration supports the following lifecycle management Actions:

Source of Identity

As a source-only system, Coupa CCW provides:

  • Contingent worker identity information synchronized to downstream systems

  • Organizational structure data (Account Segments, Cost Centers, Departments)

  • Employment status and contract details for lifecycle decisions

  • Manager relationships for approval workflows

Workflow Examples

Contingent Worker Onboarding

When a new contingent worker is added to Coupa CCW:

  1. Identity Sync: Coupa CCW provides worker details to Veza Lifecycle Management

  2. Access Provisioning: Based on department, cost center, and role, appropriate access is granted in target systems

  3. Manager Assignment: Hiring manager relationships are established for approval workflows

  4. Group Assignment: Worker is added to relevant organizational groups based on Account Segment and Department

Contingent Worker Status Changes

When a contingent worker's status changes (contract end, role change):

  1. Status Detection: Coupa CCW reflects updated employment status

  2. Access Review: Lifecycle policies evaluate continued access needs

  3. De-provisioning: If terminated, appropriate access removal is triggered in target systems

  4. Audit Trail: All changes are tracked for compliance reporting

Contract-to-Hire Conversion

When a contingent worker transitions to full-time employee:

  1. Status Update: Employment type change is detected in Coupa CCW

  2. Access Migration: Existing access is evaluated and potentially expanded

  3. System Updates: Worker identity is updated across all connected systems

  4. Process Completion: Manager and HR notifications confirm successful transition

Last updated

Was this helpful?