> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Namely

## After this article

You will be able to connect Namely to Lumos to sync employee data and use Namely as a source of user data (Source of Truth) in Lumos.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | No | Employee records synced via Merge.dev |

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 Namely 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

* **Integration partner:** Lumos partners with **Merge.dev** for the Namely integration. The connection is authorized through a Merge pop-up flow. Reach out to your Lumos CSM with further questions.
* **Permission scoping:** this is an HRIS **read** integration, Lumos syncs employee records from Namely. It does not provision or change anything in Namely.

## Read-only access vs provisioning

**Is read-only possible?** Yes, and it's the only mode. Namely is a Merge.dev-brokered HRIS integration that only reads employee records from Namely. It does not provision or change anything in Namely.

**What read-only requires.** Connect through the Merge.dev authorization pop-up as described below. There is no separate credential to choose, every Namely connection works this way.

**Watch out for.** Setting Namely as a Source of Truth changes how Lumos uses the synced data. It does not turn this into a write connection back to Namely. If a Namely field is enabled in Merge but not showing up as mappable in Lumos, that's a Merge dashboard Field Mapping issue, not an access-level problem.

## Instructions

**Phase 1: Connect in Lumos**

1. Click the Namely card in your Lumos integrations (reconnect an existing card or add a new one).
2. Click the **Connect Namely** button.
3. Follow the instructions in the pop-up that appears (Merge.dev authorization flow).

**Phase 2: Configure as a user data source**

1. After connecting, set Namely as a source of user data in Lumos via **Source of Truth** settings so employee records drive your Lumos user directory.

## Troubleshooting

**A Namely field (e.g. `employee_number`) is enabled in Merge but not mappable in Lumos.** For Merge-backed HRIS integrations, enabling a field in Merge is not sufficient. An explicit **Field Mapping** must be configured for that field in the Merge dashboard (requires Merge admin/developer access, ask Lumos support if you don't manage the Merge account). After the mapping is added, let the integration sync complete and then let the Source of Truth sync complete before the attribute becomes available.

**Attribute still missing after mapping.** Source of Truth sync errors elsewhere can delay attribute availability. Resolve any SoT sync errors and allow another full sync cycle.