> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/hris/namely.md).

# Namely

Harmony supports Namely as an HRIS data source, allowing you to keep your employee directory automatically synchronized with data from your Namely account. Once the integration is connected, employee records flow into Harmony through the standard HR integration pipeline - no manual imports or CSV uploads required.

Namely joins the growing list of supported HRIS providers in Harmony, giving your organization a reliable, hands-off way to manage employee data.

### What syncs from Namely

When you connect Namely to Harmony, the integration pulls employee records from your Namely account and keeps your Harmony employee directory up to date automatically. Synced data follows Harmony's standard HR integration pipeline, consistent with all other supported HRIS providers.

### Connecting Namely to Harmony

To set up the Namely integration, follow the steps below.

1. In Namely, click the **API** menu item and open the **Personal Access Tokens** tab. Create a token and copy it. If you don't see the **API** menu item, ask your Namely administrator for the necessary permissions. The token has the same permissions as the Namely user who creates it, so create it as a user with the Administrator access role - ideally a dedicated integrations user.
2. Note your Namely subdomain: the part of your Namely address before `.namely.com` (for example, `your-company` in `https://your-company.namely.com`).
3. In Harmony, navigate to **Settings** and open the **Integrations** section.
4. Find **Namely** under **HRIS** (or search for it by name) and click its card.
5. Enter your **Company subdomain** and **Personal Access Token**, then click **Connect**.
6. Once connected, Harmony will begin syncing employee records from Namely automatically.

After the initial sync, your employee directory will reflect the data in Namely, and subsequent changes in Namely will be picked up through the standard sync process.

### Things to know

* The Namely integration uses Harmony's standard HR integration pipeline, so behavior is consistent with other supported HRIS providers.
* No manual imports are needed once the integration is active.
* Namely Personal Access Tokens expire after 2 years, and stop working if the Namely user who created them becomes inactive or is deleted. Replace the token before either happens.
* To rotate the Personal Access Token, open the **Namely** card under **Settings** > **Integrations**, click **Replace** next to **Personal Access Token**, paste the new token, and click **Save Changes**. The **Company subdomain** of a connected integration cannot be changed.

### Supported HRIS providers

Namely is one of several HRIS providers supported by Harmony. If you use a different HR system, visit the HRIS section of this documentation to see the full list of available integrations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/integrations/hris/namely.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
