After this article
You’ll be able to connect ChartHop to Lumos and use it as a source of user data (HRIS) for visibility and access workflows. ChartHop is a Merge.dev-powered HRIS integration.Capabilities
Required plan and roles
- ChartHop role: you need Admin permissions in your company’s ChartHop instance, or someone has to share their access with you.
Read-only access vs provisioning
Is read-only possible? Yes. ChartHop connects as a Merge.dev-powered HRIS source, and Lumos syncs employee and user records from it for visibility and access workflows. No capability to create, suspend, or remove ChartHop accounts from Lumos is documented, so treat this as a read-only source of user data. What read-only requires. Admin permissions in your company’s ChartHop instance, or access shared by someone who has them, then follow the steps below to connect through the Merge.dev-powered flow. Watch out for. Because Lumos partners with Merge.dev for this integration, the underlying credential and its scope are handled inside the Merge.dev connection pop-up rather than a Lumos-visible token, so there is no separate read-only credential to choose. Consult Merge.dev’s own documentation if you need details on what that pop-up grants.Instructions
Phase 1: Connect in Lumos- Click the ChartHop card in your Lumos integrations (reconnect an existing card or add a new one).
- Click the Connect ChartHop button.
- Follow the instructions in the pop-up that appears to finish connecting the integration.
- Once you’ve connected the integration, you’ll probably want to set it as a source of user data in Lumos.
- See the Source of Truth settings documentation for the different source of truth options.