Skip to main content
The technician list shows the people who do the work: their team, home site, skills, certifications, whether they are available right now, and how loaded they are. Open it from Workforce → Technicians.
If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.
The technician list The technician list The screen has two views, switched in the header: People (the list) and Teams (the crews they belong to).

The header

Columns

Hidden columns you can add under Columns: Type (worker type), Email, Phone, Signs in as (their account, or no account), Department, Employment, Started, SLA met, Completed (in the period), Minutes owed (planned minutes outstanding), Max jobs (maximum concurrent jobs), Next expiry (next certification expiry), Can travel, Radius (travel radius in km) and Active. Search technicians matches on the name. Available now shows only those available at this moment. Filter, Views and Columns work as on every list.

Availability

Availability is never worked out on this screen. It is decided in one place — employment status first, then approved leave, then any unavailable window, then the roster — so what you see here, on the dispatch board and in routing is always the same answer. To change it, use the technician’s Availability tab.

Bulk edit

Tick rows, then Edit in a grid to change several technicians at once in a spreadsheet, one row per person. It runs as an import, which is what gives it an undo, so it needs Import access.

Adding a technician

Every technician signs in, so a technician is added from an existing sign-in account. Add technician opens Add somebody who already signs in: Adding a technician from a sign-in account Adding a technician from a sign-in account Add them creates the technician and opens their record, where you set skills, certifications and the rest. Somebody who has no login yet must first be invited under people and access; they can then be put on the roster from the same row there. The button appears only for people holding both Add technicians, teams and shifts and Invite and manage users, because deciding whose login is whose is identity administration.
A technician and a user are different records, linked. A user is somebody who signs in; a technician is somebody who does maintenance and can be scheduled. The link is what lets the product know whose work “my work” means. Users and their roles live under people and access.

Teams

Teams lists every crew with its code, its lead (“led by Raj Kumar”) and the number of members, plus scoped or role-restricted where the team is narrowed. The teams view The teams view A team is a crew that work is assigned to as a unit. The lead is who a job routed to the team lands on when nobody more specific is chosen. Crews are managed here, beside the people in them, rather than under configuration — a team is people, not a setting. Click a team to see its members. Add somebody… adds an existing technician, or an account not yet on the roster (which opens the add-technician panel with the crew already chosen). The cross beside a member removes them from the team. Edit opens the team form; Add a team creates one. The new team form The new team form Adding a team needs Add technicians, teams and shifts; removing one needs Remove technicians and teams.

Inside a technician

Skills, certifications, training, schedule, availability, work and performance.