# Namely setup

Namely connects through the **unified HRIS connector**. This page covers the
Namely-side configuration you complete first. Once it's done, add the connector
in Mesh by following [Connect your HR system](../connect-your-hr-system.md).

You finish with two values:

| Value | Where it comes from |
|---|---|
| **Subdomain** | The first label of your Namely URL |
| **Personal access token** | Admin → API |

## Before you start

You need **administrator access** to your company's Namely instance.

> **warning**

These steps reflect Axiad's current understanding of Namely's configuration.
Because Namely is a third-party product, there may be variations between your
experience and what this guide describes, depending on the version in use and
recent updates.

If you find a significant difference, or anything that doesn't make sense, let
us know through Axiad support.

## Step 1 — Find your subdomain

Your subdomain is the first label of the URL you sign in at. If you sign in at
`acme.namely.com`, the subdomain is `acme`.

![The connection window asking for the Namely subdomain](/img/connectors/hr/providers/9450063-1ba7580454.jpg)

![The subdomain entered in the connection window](/img/connectors/hr/providers/9450063-effda13bbe.jpg)

## Step 2 — Create a personal access token

1. Under the **Admin** dropdown, select **API**.

   ![The Namely admin menu with the API item](/img/connectors/hr/providers/9450063-cfec2bd86d.jpg)

2. Open the **Personal Access Tokens** tab at the top left.
3. Name the token — something identifying the Axiad Mesh connection — and select
   **Create**.
4. Copy the token.

   ![The created personal access token](/img/connectors/hr/providers/9450063-a434f60433.jpg)

## Step 3 — Connect in Mesh

Follow [Connect your HR system](../connect-your-hr-system.md), choose Namely in
the connection window, and supply the subdomain and token.

## After connecting

The connector appears in your connectors list with **Health: Initializing**
while the first collection runs, then moves to **Good**. Access is
**read-only**: Mesh does not write back to Namely.

If it doesn't come online, see [Troubleshoot HR
connectors](../troubleshoot-hr-connectors.md).

## Troubleshooting

| What you see | Likely cause | Fix |
|---|---|---|
| Authentication fails | The full host was entered instead of the subdomain | Enter only the first label, for example `acme` |
| The token was created on the wrong tab | OAuth applications and personal access tokens are different | Use the **Personal Access Tokens** tab |