Team & Access
Everyone who uses the system has their own account. What a person can see and change is decided per site, so you can give an operator full control of the terminal they run and read-only access to everything else.
The three roles
Section titled “The three roles”| Role | What it can do |
|---|---|
| Viewer | See sites, zones, measurements, history, and the 3D view. Read-only. |
| Editor | Everything a viewer can, plus draw and edit zones, capture and clear floor baselines, and record adjustments. |
| Admin | Everything an editor can, plus invite people, set roles, and manage the organization. |
The short version, as the portal puts it: admins manage, editors operate on data, viewers are read-only.
A role is always held against something — the whole organization, or one site. It is normal to be an editor on the sites you run and a viewer on the rest.
Two kinds of access
Section titled “Two kinds of access”When you add someone, you choose how far their access reaches:
- Entire organization — every site you have now and every site you add later. This is for your own staff.
- Specific site or workspace — scoped access and nothing else. This is for customers, partners, and contractors who should see one terminal without seeing the rest of your operation.
A workspace is a named group of sites — a region, a business unit, a customer’s locations. Granting access to a workspace grants it to every site inside, so you add a site to the workspace once instead of updating everyone’s access individually.
Access is additive. Someone can be a viewer across the organization and an editor on the two sites they actually run. The most permissive role that applies to a given site is the one that takes effect there.
Inviting someone
Section titled “Inviting someone”Adding people is admin-only, and Access appears in the sidebar only if you are an admin. If you can’t see it, ask an admin in your organization.
-
Open Access
Section titled “Open Access”Access in the sidebar, then the People tab. Every person with any access to the organization is listed here, with what they hold.
-
Add people
Section titled “Add people”Choose Add people and enter their email, and their name if they are new to the system.
-
Choose the access level
Section titled “Choose the access level”Entire organization for staff, or Specific site or workspace and then pick which one.
-
Choose the role
Section titled “Choose the role”Viewer, editor, or admin — as above.
-
Add them
Section titled “Add them”Someone new to the system gets an invitation email with a link to set their own password. Nobody sends or receives a temporary password.
Changing or removing access
Section titled “Changing or removing access”The People tab is also where access is changed. Each row shows what that person holds, and an admin can change their role or remove their access from there.
Removing someone’s access stops them signing in to your organization. It does not touch the site’s zones, measurements, or history — those belong to the site, not to the person who was looking at them.
Workspaces
Section titled “Workspaces”The Workspaces tab is where site groups are defined: name a workspace, add sites to it, and grant people access to the group rather than site by site. Adding a new site to an existing workspace immediately gives everyone with access to that workspace access to the new site.
Workspaces are worth setting up once you pass a handful of sites. Below that, granting per site is simpler.
Your own account
Section titled “Your own account”Your personal settings are under Settings, and every person manages their own:
- Profile — your name.
- Email — change your email address and verify the new one.
- Password — change your password.
- Sessions — every device you are currently signed in on. Sign out any you don’t recognize.
- Appearance — light or dark.
On a local portal
Section titled “On a local portal”An edge device serves its own portal on your network, but accounts are not managed there. People are created and removed in the cloud portal and synced down to the device, so add and remove access in the cloud and the site portal follows.
That sync is one-directional by design, and it is why sign-in on a site portal keeps working for roughly 30 days without a connection — see Working offline.