Site Access
Site access restricts which organization sites a member can view. Combined with a role, it defines full permissions: the role specifies "what can be done", and site access specifies "where". This ensures a technician on one farm cannot see another, and a hosting client cannot view equipment belonging to other customers. v1.0.0-alpha4
Two Access Models
| Type | Roles | How It Works |
|---|---|---|
| Global | Owner, Administrator | All organization sites, including sites created in the future. Cannot be restricted |
| Selected Sites | Operations Manager, Technician, Viewer / Customer | Only sites explicitly assigned. Newly created sites are not accessible automatically |
If a member is assigned all existing sites and a new site is added later, they will not have access to the new site until an admin assigns it manually. This prevents accidental data leaks when new facilities are commissioned.
How to Assign Sites
- During invitation — in the Add member dialog after selecting a role (see "Inviting Members"). An invitation cannot be sent without selecting at least one site, unless the role is Administrator.
- Afterwards — in the Members section via Edit role in the ⋮ menu for that member (see "Managing Members").
Sites are selected from a checkbox list showing device counts next to each site name. Selected sites are displayed as dismissible tags. Helper buttons Select All / Deselect All and a counter "Selected sites: N" simplify bulk management.
For the Administrator role, this field is locked and displays "All organization sites (Global)" with an explanation that access is automatically granted to all company sites.
What a Member with Selected Site Access Sees
- Site switcher only lists their permitted sites. Other sites are hidden and excluded from search.
- A single assigned site is automatically selected upon login.
- Dashboard, device list, agents — only reflect the active permitted site.
- Events and notifications — only generated for their permitted sites.
Navigating to an unauthorized site via direct URL is blocked on the server, and data for restricted sites is never transmitted to the client browser.
Typical Scenarios
- Multiple farms across regions — each has its own Operations Manager and technicians; each team only sees their local facility. The Owner and CTO see the entire operation.
- Mining hotel / Colocation — each client is assigned a dedicated site (or room) with their hardware, invited with the Viewer / Customer role strictly for that site.
- Contracted service provider — Operations Manager role on the contracted sites. Once the contract concludes, access is revoked by removing them from the organization.
- Commissioning a new site — assign it to the relevant members via Edit role in Members: initially, only the Owner and Administrator have access.
Notes
- Organization-wide capabilities (such as viewing the team members list) depend solely on role, not on site assignments.
- Personal accounts only have a single site, so site scoping does not apply.
Organization: Overview
Starting with `v1.0.0-alpha4`, Pulse is a multi-user system. The owner of a Business account organizes sites under an organization, invites the team, and configures permissions and accessible sites for each member.
Inviting Members
An invitation grants a user access to your organization with a specific role and set of sites. Knowing their email is sufficient: advance registration in Pulse is not required — the user account can be created upon accepting the invitation.