Sites & Locations
Organize your devices and team by physical location, and manage backup policies per site.
What Sites Are
Sites represent your physical locations — offices, branches, warehouses, client premises. Every device belongs to exactly one site, and team members can be scoped to specific sites. Your account starts with a default site; add more from the Sites page as your organization grows.
- •Each site has a name, optional address, and a storage region (US / Canada / EU).
- •Devices enrolled with a site-specific enrollment code land in that site automatically.
- •Site cards show live device and member counts; click a card to drill into its devices and team.
Creating and Editing Sites
- •In the Customer Portal, go to Sites and click Add site.
- •Enter the site name (e.g. "Downtown Office") and, optionally, its address.
- •Pick the storage region for data from this site’s devices.
- •To edit later, open the ⋮ menu in the top-right corner of the site card and choose Edit.
The Default Site
One site is always marked Default. Devices enrolled without a site-specific code are placed there.
- •To change it, open the ⋮ menu on any other site card and choose Set as default.
- •The previous default site keeps its devices — only the marker moves.
- •The default site cannot be deleted. Set another site as default first if you want to remove it.
Removing a Site
Deleting a site never deletes backups. If the site still holds devices, the portal opens a transfer wizard that requires you to move them to another site first.
- •Open the ⋮ menu on the site card and choose Delete.
- •If devices remain, pick the destination site in the transfer wizard — all devices move together.
- •Site-scoped team assignments for the removed site are cleared; account-wide roles are unaffected.
ℹ Note
Backup Policies
Policies let you define backup rules once and enforce them across every device in a site — or across all sites. Desktop agents apply the effective policy automatically on their next sync.
- •A policy contains include-path rules (what must be backed up) and exclude patterns.
- •Paths use cross-platform templates like {HOME}/Documents, resolved per-OS on each device; rules can also target a single platform (Windows, macOS, Linux).
- •Required rules are enforced and locked on the device; optional rules seed editable defaults.
- •Scope a policy to one site, or to All sites for account-wide baselines. A device’s effective policy is the merge of both.