An operator with sites in four cities and a technician in each has a problem the platform did not previously solve: every staff login saw every station. That is fine at one city and unacceptable at four, particularly once contractors and franchise partners are involved.
How it works
- A station group is a named set of stations. A station can belong to more than one.
- Staff can be restricted to specific groups. Restricted staff see only those stations everywhere — lists, maps, sessions, reports and search.
- Each assignment carries three separate permissions: view, operate and manage. A contractor can be given operate without manage, so they can reset a charger but not change its configuration.
- Owners are never restricted. That is deliberate — an account that cannot see its own network is a support ticket waiting to happen.
Enforced where it counts
The restriction is applied in the data layer rather than in the interface. A restricted user querying the API directly for a station outside their groups gets nothing, not a hidden button. Frontend checks remain advisory, as they should be.
Migration
Nothing changes for existing accounts. Restrictions are off by default and every current user keeps the access they had until someone creates a group and assigns it.
releasesecuritypartners