N-able N-central

N-able N-central is a remote monitoring and management (RMM) platform. This connector brings in the devices managed through your N-central server.

Beta. This connector was built from N-able N-central’s documentation and hasn’t been verified against a live account yet. It may return incomplete data or fail in ways we haven’t seen. If something looks wrong, contact support@chartingcyber.com.

At a glance

Required permissions

Create a dedicated user in N-central for Navigator. It needs all of the following:

• An access group that covers the customer environment you want synced. Devices outside the user’s access group are not returned.
• A read-only role with read access to Configuration, Devices and Reporting. No write access is required.
• MFA requirement turned off for the user.
• API only checked in the user’s API Access section, so it cannot sign in to the dashboard.

Setup

1. In N-central, go to Administration → User Management → Users and create the user. Assign the access group and the read-only role above.
2. Save the user first. The token can only be generated by editing a user that already exists, so you can’t create it during the initial create.
3. Edit the saved user, turn off the MFA requirement, and open the API Access section. Check API only, then click Generate JSON Web Token. Copy it — treat it like a password.
4. In Navigator, go to Connectors → Add a Connector → N-able N-central.
5. Enter your N-central server URL — the address you use to sign in to your own N-central server (for example https://ncod123.example.com; N-able-hosted servers typically begin with ncod), and the User-API Token.
6. Save. Navigator validates the credentials and enqueues a first sync immediately.

Generate the token after the role and access group are assigned. If you change the user’s role or access group later, generate a new token and save it in Navigator.

What data this connector provides

• Devices: every device N-central manages, including hostname, manufacturer, model, serial number, operating system and version, IP addresses and MAC addresses.

Known limitations

• N-central has no shared cloud address — each installation has its own server URL, so you must supply yours. It must be reachable over the public internet via https with a publicly trusted certificate. Self-hosted servers on a private network, or with a self-signed certificate, are not supported yet.
• Hardware details are fetched per device, so the first sync of a large fleet takes longer than a single-request connector.
• Users, vulnerabilities and software are not provided: N-central’s users are console/technician accounts rather than a directory.
• Storage, memory and encryption status are not collected yet.

Troubleshooting

• The sync fails with a message that the source rejected the saved credentials. N-central refused the token. Check the user is enabled, has API only checked, has the MFA requirement off, and has a read-only role and an access group assigned. Then generate a new token from the saved user and save it in Navigator.
• The sync fails with a message that access was denied. The token is valid but the user lacks a permission. Check the role has read access to Configuration, Devices and Reporting, and that the access group covers the customer environment.
• Login fails even though the setup looks right. Confirm the role assigned to the user still exists in the roles list. A user pointing at a role that has been deleted can’t log in, and N-central reports it as an unauthorized error.
• Devices sync but some are missing. They are outside the user’s access group. Add the customer environment to the group.