N-central is connected once for your whole workspace. SeatReaper reads your devices and when each last checked in, and matches them to clients by N-central customer ID.
1. Create a read-only API user in N-central
- In N-central, create a user just for SeatReaper (N-able calls this an API-only user), with a role that can view devices and customers and nothing more.
- Open Administration > User Management > Users, select the user, open API Access, and choose Generate JSON Web Token. Copy the token.
N-central's REST API needs N-central 2023.9 or later.
2. Connect in SeatReaper
Owners open Settings > Integrations, choose N-able N-central under Add an integration, enter the N-central server address (for example https://ncentral.yourmsp.com) and paste the token, then choose Connect N-central. SeatReaper tests the token, saves it encrypted, and runs the first sync.
How devices are matched to clients
Each client's N-central customer ID (under Tool IDs) is compared with each device's customer ID and site ID. Devices that match no client are kept but not shown on any client. A client whose ID matches no devices shows Not found under Data sources; check the ID.
What SeatReaper reads
Device name, class, operating system, customer and site, and the last time the device checked in. It never runs tasks, scripts or changes in N-central.
Older N-central versions (before 2025.3.1.9) leave the last check-in time out of the device list, so it shows as Never until the server is updated.
Syncing and removing
Everything syncs once a day; Sync now on Settings > Integrations syncs immediately. Disconnect deletes the saved token and every synced device. To revoke the token itself, remove the API user's access in N-central.
In compliance reports
On Growth and Pro, N-central devices are the RMM column of the Device inventory and gaps report in the compliance evidence reports. A device any tool has seen recently counts as active, and active devices with no EDR or backup are listed first.