After this article
You will be able to connect Nmbrs to Lumos to sync employee data, and optionally use Nmbrs as a source of user data for your organization.Capabilities
Account status is reconciled from the HRIS user status: Active → Active, Inactive → Suspended, Pending → Staged, and Deleted (no longer returned) → Deprovisioned. When Nmbrs is the User Source, employment status is reconciled separately: Active → Active, Inactive → Inactive, Pending → Staged, and Deleted → Inactive.
Required plan and roles
- Integration partner: Lumos partners with Merge.dev for the Nmbrs integration. Authentication is handled through a guided Merge connection pop-up rather than manually created API credentials. For more on the integration requirements, review the Merge.dev documentation.
- Permission scoping: this is a read-only HRIS integration. Lumos syncs employee records from Nmbrs but does not provision or deprovision anything in Nmbrs.
Read-only access vs provisioning
Is read-only possible? Yes, and it’s the only mode. Nmbrs is a Merge.dev-brokered HRIS integration that only reads employee records from Nmbrs. It does not provision or deprovision anything in Nmbrs. What read-only requires. Connect through the Merge.dev pop-up as described below. There’s no separate credential to choose. Every Nmbrs connection works this way. Watch out for. Setting Nmbrs as a user data source in Lumos only changes how Lumos uses the synced data. It does not turn this into a write connection back to Nmbrs. If the pop-up connection flow is closed before completing, reconnect and restart it rather than assuming a partial connection is usable.Instructions
Phase 1: Connect via the Merge pop-up- Find the Nmbrs card in your Lumos integrations (reconnect an existing card or add a new one).
- Click Connect Nmbrs.
- Follow the instructions in the pop-up that appears to finish connecting.
- After connecting, you can set Nmbrs as a source of user data via the Source of Truth settings in Lumos.