Skip to main content

​
After this article

You will be able to connect Kallidus to Lumos via the Merge.dev partnership to sync employee data, and optionally use Kallidus as a source of user data in Lumos.

​
Capabilities

As a Merge.dev-brokered HRIS integration, Lumos reconciles account status from the HRIS user status: Active → Active, Inactive → Suspended, Pending → Staged, Deleted (no longer returned) → Deprovisioned. When Kallidus is the User Source, employment status is reconciled separately: Active → Active, Inactive → Inactive, Pending → Staged, Deleted → Inactive. Attributes available for mapping in User Sources include Manager, Team, Title, Employment Type, Start Date, and Termination Date. Per-app field support varies.

​
Required plan and roles

  • Permission scoping: this is a read-only HRIS integration. Lumos syncs employee data from Kallidus but does not provision or change anything in Kallidus.
  • Authentication is handled through the Merge.dev connection flow. There are no credentials to generate in Kallidus beforehand.

​
Read-only access vs provisioning

Is read-only possible? Yes. This connector is read-only in every configuration. Lumos syncs employee data from Kallidus through Merge.dev but does not provision or change anything in Kallidus. What read-only requires. No credentials to generate beforehand. Follow the steps below to connect through the Merge.dev pop-up. Watch out for. There is no provisioning variant of this connector to switch to. Creating, deactivating, or removing employee records has to happen in Kallidus directly, since this connection only ever reads employee data into Lumos.

​
Instructions

Phase 1: Connect in Lumos
  1. Click the Kallidus card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Click Connect Kallidus.
  3. Follow the instructions in the Merge pop-up that appears to finish connecting.
  4. After connecting, you can set Kallidus as a source of user data via the Source of Truth settings.