Per-location operator access
Restrict an operator to specific locations so they only see and run their area.
What it does
By default an operator can work any of your organization's locations. Per-location access lets an admin restrict an individual operator to one or more specific locations. Once restricted, that operator only sees and can only run storms for the locations they're granted.
When to use it
- Multi-region fleets — an operator who only ever works the north yard shouldn't see, or accidentally join, a run in a location an hour away.
- Subcontractors and seasonal staff — grant access to just the properties they cover, and nothing else.
- Cleaner tablets — fewer irrelevant locations on screen means faster, less error-prone selection in the field.
How to set it
An admin grants each restricted operator access to specific locations from the member's roles/access settings. Leave an operator with no location restriction and they retain access to all locations — the restriction is opt-in per person.
How it interacts with roles
Per-location access is a filter layered on top of the operator role, not a replacement for it. The person still needs the operator role to run a machine at all; the location grant then narrows which locations that applies to. It has no effect on admins or dispatchers, who work across the whole organization.
A tip
Set this up when you onboard an operator, alongside assigning their role. It's much easier to grant the right locations from the start than to discover mid-storm that someone joined the wrong area's run.
Updated 2026-08-09
In this topic
- Organization settings overview
- Your profile
- Language (English / French Canada)
- Distance unit (imperial / metric)
- Default swarm direction
- Quiet hours for customer alerts
- Claim timing: TTL floor and silence timeout
- Geofence arrival radius
- Plow-ridge recheck tunables
- Season window
- Route-order strength (loose / balanced / strict)
- Roles and RBAC