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

# Device Mapping

> How Neo maps RMM devices to PSA companies — automatically, and how to correct it from the dashboard

When Neo syncs devices from your RMM, it links each device to the matching **PSA company** so reports, automations, and agents know which customer a device belongs to. Most devices map automatically; the **Device Mapping** tab lets you see the result and fix any that didn't.

<Note>
  This works the same across every supported RMM — Datto, NinjaOne, N-central, N-Sight, ConnectWise Automate, ConnectWise Asio, and Kaseya VSA X. The mapping is keyed on devices, not on vendor-specific sites or organizations.
</Note>

## How Neo maps devices automatically

On every RMM sync, Neo resolves each device's PSA company using the strongest signal available:

1. **Exact name match** — the device's RMM organization or site name is matched (case-insensitive) against your synced PSA company names.
2. **Asset overlap** — for devices an exact name can't place, Neo looks up their hostnames among your PSA configuration items and maps the device to the company that owns them, but only when the evidence is near-unanimous.

A device that neither signal can place is left **Unmapped**.

<Info>
  Automatic mapping can't resolve every device. Common cases: an RMM organization named differently from the PSA company (a rebrand), sites named by location code rather than company, or a PSA with few or no configuration items to match against. Those devices stay **Unmapped** until you assign them on the Device Mapping tab.
</Info>

## The Device Mapping tab

Open [**Integrations**](https://dashboard.neoagent.io/integrations), select your connected RMM, and choose the **Device Mapping** tab.

The header shows **Total devices**, **Mapped**, and **Unmapped** counts. The table lists each device with:

| Column              | What it shows                                             |
| ------------------- | --------------------------------------------------------- |
| Device              | The device name                                           |
| Organization / Site | RMM context, where the vendor provides it                 |
| PSA Company         | The mapped company (or "—" when unmapped)                 |
| Source              | How it was mapped — **Auto**, **Manual**, or **Unmapped** |
| Mapped by           | Who set a manual mapping, and when                        |

Filter by status (**All**, **Mapped**, **Unmapped**, **Manual**), by company, or by device name.

## Assign devices to a company

<Steps>
  <Step title="Filter to what you need">
    Use the **Unmapped** status filter to find devices that still need a company (or search by name).
  </Step>

  <Step title="Select the devices">
    Tick individual rows, or use the header checkbox to select the current page. When more devices match than fit on one page, click **Select all N matching** to select the entire filtered set across pages.
  </Step>

  <Step title="Assign to a company">
    In the action bar, click **Assign to company**, pick a PSA company, and confirm. Filtering to *Unmapped*, selecting all, and assigning is a single action — no paging through devices one screen at a time.
  </Step>
</Steps>

<Tip>
  The company picker lists your synced PSA companies — the same set Neo uses everywhere else. If a company is missing, run a PSA sync first.
</Tip>

### Manual assignments stick

A manually assigned device is marked **Manual** and **keeps its company through every future RMM sync** — Neo's automatic mapping never overwrites a manual choice.

### Reset to automatic

To hand a device back to automatic mapping, select it and choose **Reset to auto** in the action bar. Neo recomputes the device's company on the next sync.