Docs / Manual
Roles
Viewer, technician, expert and administrator, and what each can do.
Every user has a named account with one role. The role decides which screens and actions are offered, and the server checks it again on every request.
| Role | Typical user | Can |
|---|---|---|
| Viewer | Managers, auditors | Read answers, the sequence of events, sources, handover, journal and reports. Cannot confirm causes, record actions, report check results or review workflow results |
| Technician | Maintenance technicians, shift leads | Everything a viewer can, plus ask questions, report check results, confirm the cause, record the corrective action, rate answers, log knowledge gaps, write journal records, record part changes and review workflow results |
| Expert | The engineer who curates knowledge | Everything a technician can, plus the knowledge health view and the gap log, confirming drafted journal records, and running imports |
| Administrator | Site IT or the BooleX owner on site | Everything an expert can, plus accounts, asset codes, and the platform settings described in Administration |
Accounts are made by an administrator (Add a user) or come from the site directory over LDAPS (Accounts and sign-in).