Not required. Every plan runs the full onboarding without a single connection. Integrations come with the Practice and Firm plans. Each one is optional, connects from Settings in a few minutes, and can be disconnected at any time.
Available now
Four connections you can switch on today.
RMM: NinjaOne
Agent check-ins tick the rollout tasks on their own, and each device is matched to the person who uses it. A person reads as onboarded once their computers report in.
Documentation: Hudu
Each verified credential is filed in Hudu by reference. The secret itself is never stored here. A password changed in Hudu reads as a rotation on the ledger.
Microsoft 365: sign-in and calendars
Your team signs in with Microsoft through your own Entra app. Engineers connect their calendars, bookings land on them, and every session carries a Teams link.
Microsoft 365: people census
Each client’s people, read from their own Microsoft 365 instead of a spreadsheet. Choose who counts by license, department, domain or group, then sync them to the people list. Read only: the client’s administrator approves it once, and their contact confirms the list in their portal.
Coming later
On the list, in the order MSPs ask for them. Nothing below is part of a plan yet.
PSA: HaloPSA, ConnectWise, Autotask
Agreements seeding each plan, and onboarding time and notes written back to the ticket. HaloPSA first, then ConnectWise and Autotask.
RMM: Datto RMM, N-able N-central
The same agent check-in tracking NinjaOne has today.
Documentation: IT Glue
Credential and document filing by reference, as with Hudu.
Microsoft Bookings
Sessions offered as real bookable slots in Bookings, beside the portal’s own booking.