Onboarding clients

Onboarding a new client means two things: getting the BareNOC Connect installer onto their machines, and adopting those devices into your console.

BareNOC Connect

BareNOC Connect is the small endpoint installer each client runs on their Windows PC. It registers the machine with your console, joins your tailnet (or LAN), and lets your agent chat run real checks against it.

• Generate a join link/invite from Onboarding → Invites.
• The client downloads the Connect installer and runs it — no admin skills needed.
• Once joined, the machine appears under Devices in your console.

Silent join vs owner login

• Silent join — the installer is pre-seeded with your invite token, so the client just clicks Next. No credentials to type, no account to create. Best for most clients.
• Owner login — the client signs in with their own email invite (or a shared tenant login). Best when the client wants to see their own reports/session logs.

Both modes end the same way: the device is adopted and visible to you.

Email invites

Send an invite by email from Onboarding → Invites → Send. The email contains a one-click join link that either pre-fills the silent-join token or starts the owner-login flow, depending on the invite type you picked.

Adopting devices

Adoption is the step where a joined machine becomes a managed device with its own session log and report history. You can adopt:

• From the console — select the machine in Devices and choose Adopt.
• Automatically — turn on auto-adopt for a client so any Connect-joined machine is adopted without a click.

After adoption the device shows health, checks history, and becomes available to the agent chat and reports.