Workspace setup

Overview

The administrator module. Five tabs cover user accounts, stations, service providers, roles and module access, and the reference values every other module draws its dropdowns from.

Step by step

Work through these in order the first time. After that, steps two to four are the daily loop.

1. 01

   Create stations before people

   Station access is assigned per user, so the stations have to exist first. Add the country too — it appears in reporting.

2. 02

   Define roles before accounts

   A role is a named set of visible modules plus a provider flag. Build the three or four roles your operation actually has, then create accounts against them, rather than tuning access per person.

3. 03

   Add provider companies and their stations

   A provider company carries the list of stations it covers. Provider users are then scoped to work rolled out to their company, at those stations — nothing else is visible to them.

4. 04

   Create users with the narrowest scope that works

   Each account gets a role, a user type, and its station list. Grant the stations the person actually works at; widening later is a two-click change.

5. 05

   Fill in the reference values last

   PM types, asset types, fuel types and locations populate dropdowns across every other module. Asset types matter most — each carries the checklist key that decides which inspection an asset receives.

6. 06

   Reset passwords from here

   Administrators can reset a password without knowing the old one. Users change their own from the account menu in the top bar.

Notes from the field

Behaviour that is easy to miss from the interface alone.

Full capability list

Everything workspace setup can do, as shipped.

• User accounts — create, edit and delete, with role, user type, station access and provider company
• Administrator password reset, alongside self-service password change for every user
• Stations and their countries
• Service-provider companies and the stations each one covers
• Roles and access — per-role module visibility, and a provider flag
• Reference values — PM types, asset types with their checklist keys, fuel types and locations