Skip to main content
The same customer company exists in many of your systems — your PSA, your documentation platform (IT Glue), your RMM, Microsoft 365 — each under a different ID and often a slightly different name spelling. “Tool Supply, Inc.” in your PSA might be “Tool Supply Inc” in IT Glue. Company Mapping is the directory Neo builds so it knows these are all the same real-world company. With it, Neo’s agents read each system by its real ID instead of guessing from a name search — which is faster and far more reliable.

​
Why it matters

Without a mapping, an agent that needs a company’s IT Glue documentation has to search IT Glue by name. That breaks constantly: a name like “Craig, Deachman & Associates” or “Tool Supply, Inc.” won’t match because of punctuation differences, and abbreviations or word-order changes miss too. Company Mapping resolves the company once, stores the link, and hands the agent the exact ID — so lookups just work.
You don’t have to set anything up. Neo builds the mapping automatically as it syncs each integration. The pages below are for seeing what got mapped and correcting the occasional miss.

​
How Neo maps a company

Neo resolves each external entity (e.g. an IT Glue organization) to one of your PSA companies using a ladder of methods, strongest first. The first confident match wins: The mapping is built during sync (in the background, over your whole company list at once) and read instantly at runtime. An AI match is deliberately kept below the bar for automatic use — it shows up for you to confirm rather than silently steering the agent.

​
Where you see and manage it

​
On the Companies page

Each company row has a Linked Systems column showing the systems it’s mapped to (e.g. its IT Glue organization). Click an entry to jump straight to that integration’s mapping table. To add a mapping from here, click Map system on the row. Pick the system, then the organization that belongs to this company — the same manual mapping the Organization Mapping tab writes, without leaving the page. Microsoft 365 works differently: set a company’s tenant from its actions menu with Microsoft tenant…, or with Map GDAP tenant if you use GDAP. Several sites of one customer can share a tenant. If a tenant is on the wrong company, tick Take it off in the same dialog: the wrong company loses it, and this one takes over its Microsoft 365 access. If you use CIPP, a company with a confident CIPP match shows Through CIPP, and it needs no GDAP or Grant access, because your agents work through your CIPP instance. Confirm CIPP tenants on the Companies page lists the companies whose CIPP tenant can become their Microsoft tenant. A confirmed tenant also serves Partner Center seats, the Teams end-user bot and this page. Untick any company whose name matches the wrong tenant.

​
On the integration’s “Organization Mapping” tab

Open a connected documentation integration (e.g. IT Glue) and switch to the Organization Mapping tab. You’ll see every organization with:
  • the PSA company it maps to,
  • a Source badge — Auto (Neo matched it), Manual (you set it), or Unmapped (no confident match yet),
  • how the auto-match was made and its confidence,
  • who set a manual mapping, and when.
1

Find the organization

Use the status filter (All / Mapped / Unmapped / Manual), the company filter, or search.
2

Map or re-map it

Click Map (or Re-map) and pick the correct PSA company. This is a Manual mapping — it wins over any auto-match and survives future syncs. Only an admin or owner can map, re-map or reset an organization.
3

Reset if needed

Reset drops a manual mapping and returns the organization to Neo’s automatic matching on the next sync.
For IT Glue, the organization’s documents pick up the new company on the next daily documentation sync. Until then a company-scoped documentation search still uses the previous company.For an RMM, the organization’s devices pick up the new company on that integration’s next device sync. Until then a device-scoped action — running a script on a device, or listing a company’s devices — still sees the previous company. To move a device right away, map it in the Device Mapping tab.
Unmapped means Neo hasn’t confidently matched that organization to a PSA company yet — most often because the company isn’t in your PSA, the names are too different, or that system hasn’t finished syncing. Mapping it manually fixes it immediately.

​
Through Neo Support or the public API

Ask the Neo Support agent, for example “map the CIPP tenant Contoso Ltd to Contoso”. It lists the integration’s organizations and tells you the change. Say yes. With the default Neo Support permissions it then shows an approval card, and the mapping changes only after you approve it. The result is the same Manual mapping the tab writes. From your own scripts, use the public API with an API key: Full request and response details are in the API reference.

​
Supported systems

Every documentation platform and RMM Neo syncs has company mapping, and so do the security platforms Huntress and ThreatLocker: each one’s organizations appear in the Linked Systems column and get their own Organization Mapping tab. Microsoft 365 is mapped by its tenant instead — see GDAP. LogicMonitor has no customer record, so Neo maps each client’s resource group, first by the autotask.accountid its Autotask integration routes alert tickets by. Cloud marketplaces such as Pax8 and Ingram Micro have an Organization Mapping tab too. One marketplace customer can bill several PSA companies, for example a client’s sites. On a marketplace tab, Re-map moves the customer, so every other company loses it, Add company maps it to one more company and keeps the others, and Reset on a row removes only that company. A mapping there decides whose licences Neo buys or cancels, so Neo uses only a mapping you set or confirmed, or a match where the marketplace name is the same as exactly one PSA company. Every other suggested match waits for you to confirm it. A technician can also confirm one from an agent’s approval request for a seat change; Neo then saves it as a manual mapping with the approver’s name (Confirming a Match on Approval). Trend Micro LMP works the same way: when a ticket’s company has no mapping yet, the agent asks a technician to confirm the record on the approval card, and approving saves it.

​
FAQ

Do I need to map companies before agents can use them? No. Neo maps automatically during sync; agents use whatever’s mapped and fall back to a normal lookup for anything that isn’t. Will a re-sync overwrite a mapping I set by hand? No. Manual mappings always win and survive re-sync. Use Reset if you want Neo to take over again. An organization shows the wrong company — what do I do? Open the Organization Mapping tab, click Re-map, and choose the right company. From the other side, Map system on a company row does the same, except on a marketplace: there it adds the company, and the customer’s other companies keep it. Your correction sticks.