Lucca

Connecting Lucca to Ploy lets Ploy automatically sync your employee directory from Lucca. Ploy keeps employee records, joiners and leavers, employment dates, and reporting lines up to date, so onboarding, offboarding, and access reviews always work from current HR data.

This integration is read-only: Ploy only reads data from Lucca and never makes changes in your Lucca account.

What Ploy syncs

Ploy scans your full Lucca employee directory, including former employees, and syncs:

• Employee profiles: first name, last name, and job title

• Employment dates: contract start and end dates, used to detect joiners and leavers

• Organisation structure: department, business unit (from the Lucca legal entity), and employment type (from the Lucca principal role)

• Managers: each employee's manager, so reporting lines stay accurate in Ploy

• Employment status: an employee whose contract end date has passed is treated as offboarded

Ploy also records each employee's Lucca account itself, so Lucca shows up as an app with its users in your access map.

You can customise where each Ploy employee field comes from — including Lucca custom fields — using the optional field mappings step described below.

Prerequisites

• Admin access to your Lucca account, so you can generate an API key

• Your Lucca HR domain, e.g. company.ilucca.net

• Admin access to your Ploy dashboard

Generate an API key in Lucca

1. Follow Lucca's guide to generating an API key: Generating an API key

2. Make sure the key can read employee data — Ploy reads the Lucca users list (including former employees) and the list of user properties (custom fields).

3. Copy the key somewhere safe — you will paste it into Ploy in the next section.

Connect Lucca to Ploy

1. In Ploy, go to the Integrations page and click Configure on the Lucca integration.

2. Follow our setup instructions — the first step links back to this guide.

3. Lucca HR Domain (required): enter your Lucca domain, e.g. company.ilucca.net. Do not include http:// or https://.

4. Paste your API Key (required): paste the API key you generated in Lucca.

5. Do you want Ploy to store employee's personal emails (optional): choose Yes or No. This is useful if you do onboarding with passcodes — if no company email is found, Ploy will also use the personal email as the primary user email.

6. Continue to the next step to optionally customise field mappings, or save to finish.

Customise field mappings (optional)

The second step of the wizard lets you override how Ploy maps Lucca fields into Ploy employee fields. If you skip it, Ploy uses these defaults:

• First name from firstName

• Last name from lastName

• Job title from jobTitle

• Employment start date from dtContractStart

• Employment end date from dtContractEnd

• Department from department

• Business unit from legalEntity

• Employment type from rolePrincipal

Some Ploy fields — team, working location, location country/region/city, role level, personal email, and employee ID — have no default source and only sync once you map them to a Lucca field here.

As well as the Lucca standard fields, you can map Ploy fields to your Lucca custom user properties. Text, date, and list-type custom fields are supported, and they appear in the dropdown once your API key is saved.

What Ploy can change in Lucca

Nothing. The Lucca integration is read-only — Ploy never creates, updates, or removes anything in your Lucca account.

Troubleshooting

• "Lucca authentication failed - check API credentials": the API key is invalid, expired, or revoked. Generate a new key in Lucca and paste it into the Lucca integration settings in Ploy.

• Domain errors: the Lucca HR Domain must be your ilucca.net address (e.g. company.ilucca.net) entered without http:// or https://.

• Custom fields missing from the field-mapping dropdown: check the API key can read user properties in Lucca, and note that only text, date, and list-type custom fields are supported.

If you run into anything else, contact us through the in-app chat and we will help you get connected.