Why integrate your people data?
Once your employee data is in PlusPlus, users can sign in, get assigned to groups, receive content automatically, and have their activity tied back to a complete user record. Pulling in attributes like department, title, manager, and hire date unlocks features that depend on knowing who someone is and where they sit in the org:
Users engage more when they see colleagues' photos, titles, departments, locations, and reporting relationships.
Reports filter and aggregate by employee attributes for richer organizer insights.
Managers see and manage their directs' activity once manager-direct relationships are established through Manager's Email.
Automated rules use employee data to manage groups, enroll users into events, and assign tracks. Onboarding rules require Hire Date, and rules can match on any custom field your integration provides.
How it works
People integration moves user data from your HRIS or identity provider into PlusPlus on a recurring basis. Three things happen on every sync:
Data flow. Depending on the method, PlusPlus either fetches data from your system on a schedule, or your system pushes data to PlusPlus.
Attribute mapping. Incoming fields are mapped to PlusPlus user attributes using JMESPath expressions.
User updates. Users are created, updated, or deprovisioned based on the latest data.
Choose your integration method
We recommend an API-based integration whenever possible. Workday and SCIM are configurable in System Settings without engineering work, and are more reliable than file-based syncs. CSV over SFTP is supported as a fallback for environments where no API option is available. Custom Integrations are available for source systems that don't fit the other categories, but require an engineering engagement to scope and build.
Your source system | Use this method |
Workday HRIS | |
Okta, OneLogin, or another SCIM-capable identity provider | |
Your environment doesn't support an API-based integration | CSV over SFTP (fallback) |
Your HRIS or identity system doesn't fit any of the above | Custom Integration (engineering-scoped, contact your CSM) |
You can also pair SCIM with Workday or another method that provides the full HR attribute set. SCIM provisions and deprovisions users in real time but covers only required attributes. Pairing it with a richer source layer adds optional and custom attributes for richer reporting and automated rules.
Compare methods
| Workday | SCIM | Custom Integration | CSV over SFTP (fallback) |
Data flow | We fetch from you | You push to us | We fetch from you | You push to us |
Sync frequency | Daily | On demand | Daily | Daily |
Required attributes | ✓ | ✓ | ✓ | ✓ |
Optional attributes | ✓ | — | ✓ | ✓ |
Custom attributes | ✓ | — | ✓ | ✓ |
Configurable in System Settings | Yes | Yes | Mappings only | Yes (mappings) |
Setup timeline | Self-serve | Self-serve | Engineering engagement | CSM-assisted |
Employee data
Each employee record can include the fields below. Only Full Name and Email Address are required.
Field | Description | Required? |
Full Name | Full name of the employee | Yes |
Email Address | Primary email of the employee | Yes |
Picture URL | URL pointing to the employee's profile picture | No |
Employee ID | Identifier from your HRIS | No |
Hire Date | Date the employee joined (YYYY-MM-DD) | No |
Termination Date | Date the employee left (YYYY-MM-DD). Triggers deprovisioning. | No |
Department | Department name | No |
Title | Job title | No |
Location | Logical name of the employee's physical location. Must match a configured PlusPlus location, otherwise the field is left blank. | No |
Manager's Email | Primary email of the employee's manager | No |
Custom attributes | Business Unit, Cost Center, Last Promotion Date, and so on | No |
Set up your integration
Pick the method from the table above and follow the matching setup guide:
Workday — PlusPlus fetches user data from your Workday HRIS daily using Report as a Service (RaaS). Configurable in System Settings.
SCIM — Real-time provisioning and deprovisioning from SCIM-capable identity providers like Okta and OneLogin. Configurable in System Settings.
Custom Integration — Tenant-specific integration written by PlusPlus engineering for source systems that don't fit the other categories. Contact your CSM to scope.
CSV over SFTP (fallback) — Daily CSV upload to a PlusPlus SFTP repository. Use only when an API-based integration is not feasible.
Operate your integration
Validate and monitor
The People Integration Syncs dashboard lets you run dry-run syncs, inspect raw payloads, debug attribute mappings, and trigger manual syncs. Run a dry run before every configuration change.
Dashboard support varies by method:
Workday and Custom Integration — full dry-run, payload inspection, and manual sync.
CSV over SFTP — full dry-run capability, with one caveat: the dashboard operates on the most recently uploaded file in the SFTP repository. Re-upload a file before each dry run, since the process consumes the file when it runs.
SCIM — no dry-run support. To validate a SCIM integration, push a user change from your identity provider and confirm the user's fields update in PlusPlus as expected.
Combine methods
For organizations that want both real-time provisioning and rich attribute coverage, SCIM can be paired with Workday or another full-attribute integration method. SCIM delivers required attributes and immediate provisioning/deprovisioning when a user is added or removed in your identity provider, and the paired method layers optional and custom attributes — department, manager, hire date, custom HR fields — on top through the daily fetch. This is useful when your IdP doesn't propagate the full set of HR attributes you need for reporting and automated rules.
Map attributes
All people integration methods map the incoming payload to PlusPlus user fields using JMESPath expression syntax. Mappings are editable from System Settings > Integrations > People and can be tested via the People Integration Syncs dashboard. For complex mappings, work with your CSM or support — incorrect mappings are the most common cause of failed syncs.
Remove users
Removing a user through people integration immediately suspends their access. Anonymization, event reassignment, and full deprovisioning follow a configurable quarantine period. See People Integration: User Deprovisioning for the full lifecycle.