Sites & Locations

Sites represent physical office locations for a client. Multi-site clients — law firms with branch offices, manufacturers with multiple facilities — are a common MSP scenario.

What a site is

A site is a physical location belonging to an account. It has its own address, device count, and employee count. Sites are used to:

• Track device inventory per location
• Understand employee-to-device ratios at each office
• Support per-site billing models (e.g., $X per site/month)
• Scope RMM device imports to a specific location

Multi-site clients

A common scenario: a legal firm with a main office and two branch locations. You create one account (“Acme Law Group”) and three sites:

• Headquarters — 450 Park Ave, New York (Primary) — 35 devices
• Boston Branch — 100 Federal St, Boston — 12 devices
• Chicago Branch — 77 Wacker Drive, Chicago — 8 devices

The account's total device count aggregates across all sites. RMM syncs assign devices to specific sites where the hostname or location data is available.

Creating and managing sites

On the account detail page, go to the Sites tab and clickAdd Site. Fields:

• Site name (e.g., 'Headquarters', 'Boston Branch')
• Full address (street, city, state, zip, country)
• Is Primary — marks the main location
• Device count — manually set, or auto-updated by RMM sync
• Employee count — for this location
• Notes

Device count per site

When your RMM integration is connected, devices are automatically assigned to sites based on the location data in your RMM. The device count per site updates during each RMM sync.

If a device can't be mapped to a specific site, it's assigned to the account directly (no site). You can manually reassign devices to sites from the Devices tab.

Sites and contracts

When a contract uses per-site pricing (e.g., $X per site per month), the service line usesUnit Type: PER_SITE with a quantity equal to the number of sites. Adding a new site for a client should trigger a contract amendment (either manually logged or automatically via a workflow).

Seat reconciliation compares contracted device counts against actual device counts across all sites. This is how you catch billing drift when clients add devices at a new office without updating the contract.