Before you begin
- An Enterprise plan or above. The Integrations hub is locked below Enterprise
- The Administrator role in Atlas to connect, configure or disconnect a connector. Integrations appears under Administration only for administrators
- A tenant selected in the tenant picker. Credentials are stored encrypted per tenant, so each tenant you manage connects its own account
- An N-central server whose web address is reachable from the internet (Atlas does not connect to private or internal addresses)
- An N-central User-API Token (JWT) for a user that can read customers and devices
What you can do
- See every N-central device with its class, operating system and customer, and jump from a device to the matching session host in Atlas.
- See how many devices, probes, customers and sites you have.
- Browse your customers and sites, with each site's parent customer and location.
- Sync N-central devices into Atlas Vault as assets, every hour.
Step 1: Create a User-API Token in N-central
In N-central, go to Administration → User Management → Users, open (or create) the user Atlas will act as, and generate a token under API Access. Use a user whose role can see the customers and devices you want in Atlas. Copy the token (a long JWT). See N-able's API quick start for details.
Step 2: Connect in Atlas
Once connected, the card shows Manage, which opens the N-able N-central page, and Disconnect. The token is stored encrypted.
- Select the tenant in the tenant picker.
- Go to Administration → Integrations and click Connect on the N-able N-central card.
- Enter the Server URL (your N-central address, starting with https://, for example https://ncentral.example.com) and paste the User-API Token (JWT).
- Click Connect. Atlas signs in with the token and reads your customers before saving anything; if N-central rejects it, nothing is stored.
What you see
- Overview: Total Devices, Probes, Customers and Sites.
- Devices: name, class, operating system and customer. Search by name, class or customer, sort any column, and click the AVD link to open the matching session host. A device links when its name matches a VM name exactly, or when its short name matches exactly one VM.
- Customers: each customer and site, with its type and location. Sites show their parent customer.
Atlas reads N-central live each time you open a tab or click Refresh; the page does not copy your RMM data into Atlas. Asset sync into Atlas Vault is separate and runs only if you set it up.
Sync devices into Atlas Vault
With N-central connected, open Atlas Vault → Assets → RMM & PSA sync and click Add sync: pick N-able N-central as the source, a device class, and the asset template each device becomes, then map fields. Atlas then creates and updates a Vault asset for each device every hour, or when you click Run now. Fields you can map include the device's name, class, OS type, description, customer and site. Values someone edits by hand in Vault are never overwritten. Setting up a sync needs a Vault admin and at least one asset template.
What the integration does not do
- It is read-only. It does not change anything in N-central.
- It does not show N-central alerts or device online status, and there is nothing to acknowledge or resolve.
- It does not run automation policies or scripts, open a remote session, or patch. Use N-central for those, or Atlas Reach.
- It does not create tickets.
- There is no Atlas API key scope for N-central.
- It connects one N-central server per Atlas tenant, and cannot reach a server on a private network.
- Credentials cannot be edited in place: disconnect and connect again with the new token.
- Atlas Advisor can tell you whether N-central is connected, but does not answer questions about devices.
GCC High tenants
On a tenant or deployment in Azure Government (GCC High), calls to N-able N-central are blocked by default, because they can carry VM, host-pool and tenant names to a service outside the Government boundary. Connect fails with an Azure Government (GCC High) egress boundary message and nothing is stored, and pages that read from N-able N-central stay empty. The operator who runs your Atlas deployment can approve N-able N-central as a destination that is allowed to receive that data; once approved, the connector works normally. Running in Azure Government does not by itself make a third-party integration GCC High or CMMC compliant.
Disconnecting
Click Disconnect on the card and confirm. Atlas deletes its stored copy of the token and pauses any Atlas Vault asset sync from N-central. Assets already in Vault stay; turn the sync back on after you reconnect. Nothing changes in N-central. Revoke the token in N-central too if you no longer need it.
Troubleshooting
- N-able N-central rejected the supplied credentials: the token is wrong, expired or revoked, or its user cannot read customers.
- Could not connect to N-able N-central — verify the server URL and credentials: check the address, that it is reachable from the internet with a valid certificate, and that the server is up.
- The N-able N-central server URL is not allowed: the address resolves to a private or internal IP address.
- The Devices tab is empty when you expect data: click Refresh. An empty tab can also mean N-central returned an error; if it persists, disconnect and connect again to re-test the token.
- Asset sync reports the integration is not configured: N-central was disconnected. Connect it again, then turn the sync back on.