Kandji vs Rippling IT for a Multi-Site Property Manager

A site office's computer is usually shared among the on-site staff, while a regional property manager's laptop is assigned to one person. Those need different policies: a shared device needs a generic login with restricted permissions, while an assigned device can be tied to one person's identity and access level. Sort your fleet into these two categories before picking a platform, since the answer changes what you're actually configuring.

Include the inspection tablets in this inventory too, since they're easy to overlook until one goes missing. A site with three tablets rotating between leasing agents needs a clear answer for who's responsible for each one on a given day, not just a device policy.

If site offices run Windows, which is common given how much property management and accounting software is Windows-first, Rippling IT is the realistic starting point since Kandji doesn't manage Windows at all. A property manager standardized entirely on iPad for inspections and Mac for the regional office is the one case where Kandji's depth on those platforms could make sense instead.

Either way, price the decision against what a dedicated technical hire would cost you first. National wage data puts the median salary for a software developer, a reasonable proxy for the kind of technical role a property manager might otherwise post for, at $135,980 a year¹, which is well above what a platform subscription runs across even a large site count.

A regional manager who assumes every site's fleet already matches the standard template, and rolls out a new configuration without checking first, tends to find out mid-rollout that two sites are running an older operating system that can't take the new restrictions, or that a site's printer setup depends on a network configuration the new policy would break. Confirming state before pushing changes avoids turning a routine rollout into an emergency call from a site manager mid-day.

A useful habit is rolling any policy change out to one pilot site first and letting it run for a few days before pushing it everywhere. A site manager who hits a snag on a pilot site is a manageable problem; the same snag hitting every site on the same afternoon is not.

A site office an hour from the regional headquarters can't wait for someone to drive out every time a shared computer needs a password reset. Remote management should get a technician into that machine without a site visit for anything short of a hardware failure, which is the entire point of centralizing this in the first place rather than leaving each site to fend for itself.

Test this before you actually need it, not during a real outage. Walk through a mock password reset or software issue on a test device and confirm your remote tools actually reach it the way you expect, since discovering a gap in coverage during a live problem is far more costly than finding it during a dry run.

The most common mistake is treating each new property or site office as its own project, configured from scratch by whoever's available that week. Build a standard configuration once, apply it to every new site the same way, and a newly opened property's office is protected from day one instead of during a scramble weeks later.

Say your company adds a new property to the portfolio next quarter. Under a standardized process, the site office's computer and inspection tablets arrive pre-configured to the same baseline as every other site, and the leasing team is working with protected devices on their first day rather than whatever was quickly set up the week before opening.

Document the standard configuration itself somewhere durable, not just in one person's head. A property manager that grows past its original regional operations lead needs that checklist to survive the transition, and a written standard is far easier to hand off than tribal knowledge.

A repeatable multi-site rollout follows this order:

1. Inventory each site to separate shared computers, which get a generic restricted login, from assigned laptops tied to one person's identity.
2. Pick the platform based on what the site offices run, since Kandji does not manage Windows at all and Rippling IT covers that fleet.
3. Set up remote repair before you need it, so a technician can reset a shared computer without driving to the site.
4. Build one standard configuration and apply it to every new site before it opens, so the office is protected from day one.