Every client has a setup checklist on its page. Open it from Clients by selecting the client's name. The list on Clients shows each client's progress, such as Setup 3/7.
The items
| Item | Done when |
|---|---|
| Client added | Always done once the client exists |
| Microsoft 365 tenant ID recorded | The client has a tenant ID |
| Connect Microsoft 365 | An admin of the client's tenant approved SeatReaper and a sync ran |
| N-central customer ID recorded | The client has an N-central customer ID |
| N-central devices found | N-central is connected and devices matched this client's customer ID |
| Cove Data Protection customer recorded | The client has a Cove customer |
| Cove backup devices found | Cove is connected and backup devices matched this client's customer name |
Progress counts all seven items. A client that does not use one of the tools will simply not complete that item.
Datto RMM, NinjaOne, Datto SaaS Protection, CrowdStrike, SentinelOne, Webroot, Huntress, Sophos Central, Duo, Acronis, Flowroute and Pax8 need no IDs: they match clients by name (or by domain, for Datto SaaS Protection, and by number alias, for Flowroute), and you pick the client under Settings > Integrations for anything that did not match. See the Setup guide for IT engineers.
Why the IDs matter
SeatReaper finds waste by matching the same person or device across tools. The IDs tell it which tenant, RMM customer and backup customer belong to the same client.
See Adding a client and finding its IDs for where to find each one.
Connections
- Microsoft 365 is connected per client, from the client's page. See Connecting Microsoft 365.
- N-central and Cove are connected once for every client under Settings > Integrations. See Connecting N-central and Connecting Cove Data Protection.
Every connection is read-only; see Security and data. Changes from SeatReaper are opt-in; see Removing licenses from SeatReaper.
Archived clients
Archived clients keep their IDs and checklist. Restoring a client uses one of your plan's client slots again.