Sites

A site is a physical location your equipment lives at, like a campus, a building, or a floor. Sites let you organize your devices and gateways by where they are, watch the health of a whole location at a glance, and (if you manage your workspace) limit what a teammate sees to just their site.

Do you have this?

Sites are a plan feature. If you don't see Sites under Operations in the sidebar, your provider hasn't enabled multi-site for your workspace. Ask them if you'd like it turned on.

What sites are for

Group your devices, gateways, and networks by location so you can:

• Organize by place. Build a location hierarchy that mirrors the real world, up to three levels deep (for example campus, building, floor).
• Monitor a location. The Sites page is a live tree: each branch shows how many of its devices are online, and how many active alarms and warnings sit anywhere beneath it.
• Filter your fleet. On your device and gateway lists, pick a site to see only the equipment at that location, with a Site column showing where each item sits.
• Limit what a teammate sees. A Workspace Admin can tie an Operator or Viewer to a single site, so they only ever see that location's equipment and readings.

A device or gateway belongs to one site at a time, the place it currently lives.

Who can do what

Role	What they can do
Workspace Admin	Create, edit, and delete sites, and attach devices and gateways to them.
Operator and Viewer	Browse the site tree and filter by site, but cannot change anything. A teammate tied to a site sees only that site.

Permission required to make changes: Workspace Admin.

Create a site

1. Go to Operations -> Sites.
2. Click Create site.
3. Name the site (required).
4. Optionally set a parent site to nest it under another location, a description, a postal address, and an on-site contact (name, phone, email).
5. Click Create.

You land on the site's page, ready to attach networks, devices, and gateways.

When you save an address, we look up its map coordinates in the background. That lets equipment at the site inherit its location (see Inherit a site's location) without you placing each device by hand.

Nesting sites

Sites nest up to three levels, so you can model campus -> building -> floor. When you create or edit a site, choose its parent site to place it in the hierarchy. When you add a child under a site that already has an address, you can copy the parent's address to save retyping it.

You cannot nest beyond three levels, and a site cannot be its own ancestor.

The site tree

The Sites page shows your locations as a live monitoring tree:

• Branches (sites and the networks within them) carry rolled-up badges: how many devices are online out of the total, a red alarm count, and an amber warning count, each summed over everything beneath that branch.
• Leaves (devices and gateways) show a status dot, green for online, gray for offline, amber for a warning, and a red pulsing dot for an active alarm, with an ALARM tag on alarming devices.
• Search filters the tree to matching sites, networks, and devices and expands to show the hits.
• Click a site to open its detail page, a network to open the network, or a device or gateway to jump straight to it.

The site detail page

Opening a site gives you everything for one location in one place:

• The address sits under the site name, with Site contact details alongside the equipment cards.
• Counts show how many networks, devices, and gateways the site contains.
• Child sites, Networks, Devices, and Gateways tabs list what is attached. Device and gateway rows show their health, the same online/offline indicator used on your device lists.
• Edit details changes the name, description, address, contact, or parent; Delete removes the site.

Use the breadcrumb at the top to get back to the full Sites list.

Attach devices and gateways

There are three ways to put equipment at a site. They all do the same thing, so use whichever fits the moment.

From the site page

On the Devices or Gateways tab, click Add devices (or Add gateways), pick from the list of equipment in your workspace, and add the ones you want.

In bulk from your device list

1. Open your device or gateway list (under Fleet).
2. Narrow it with the search box and the site filter (for example No site to find equipment not yet placed).
3. Tick the rows you want.
4. In the bar that appears, choose a site under Set site and apply it to the selected rows, or to every row matching your current filter.

From a device or gateway

On a device's or gateway's Location screen there is a Site field above the Network field. Pick a site to place the equipment, or clear it to leave it unsited.

Inherit a site's location

If a site has an address, its equipment can borrow the site's map location, so a device shows up in the right place without you typing coordinates. This is always optional and you are asked first, never applied automatically:

• Bulk assign: when you set a site on selected equipment and that site has a location, you are asked whether to also apply the site's location. You can cancel, set just the site, or set the site and apply its location. Applying it fills in only the rows that have no location yet; anything already placed is left untouched.
• From the Location screen: when you pick a site that has a location, you are offered to use it. If the device or gateway has no location, this drops its pin at the site's address; if it already has one, you can choose to move it to the new site or keep its current spot. Either way you can still drag the pin to fine-tune it before saving.

In bulk, equipment that already has its own location is never overwritten. On a single Location screen you can choose to move it, but only when you confirm.

Sites and networks

A network can belong to a site. When it does, every device and gateway in that network takes its site from the network automatically, so a grouped device's site follows its network. Because of that:

• A device or gateway that is in a network shows its site as read-only on the Location screen, with a note that the site follows the network. To change it, move the network, or remove the equipment from the network first.
• When you put a device into a network, it can only join a network that sits at the same site. The Location screen and the add-equipment pickers only offer networks that match, so you cannot accidentally break the location structure. Equipment with no site yet can join any network and takes on that network's site.

Limit a teammate to a site

If you're a Workspace Admin, you can tie an Operator or Viewer to a single site so they only ever see that location. This is set on the Members list (see Account settings):

• When inviting or editing an Operator or Viewer, set their Site access to a specific site, or leave it on All sites.
• A member tied to a site sees only the devices, gateways, networks, dashboards, readings, and alerts within that site and the sites nested under it. Everything else is hidden.
• Promoting a restricted member to an admin role clears the restriction, since admins see the whole workspace. You'll be asked to confirm this.
• Changing a member's site access signs them out of their current session, so the new view takes effect the next time they sign in.

Where each reading was taken

Each reading records the site the device was at when it arrived. This shows up as a Site column:

• On a device's Events tab, every uplink, downlink, and log entry shows its site.
• In a History table dashboard widget, a Site column appears when the readings in view span more than one site, which happens when a device has moved between locations during the window.

Because the site is recorded at the moment each reading arrives, a device that moves keeps the older readings attributed to where they were actually taken. If a site has since been deleted, those older readings show (deleted site).

Remove and delete

• Take equipment off a site. On the site page, remove a device or gateway, or clear its Site field from the Location screen. It stays in your workspace, just unsited.
• Delete the site. On the site page, click Delete. A site cannot be deleted while it still has child sites or while a member is tied to it, so move or reassign those first. When a site is deleted, the networks, devices, and gateways at it become unsited; they are not deleted.