Roles and permissions

WorkOrder V3 is designed around operational handoff. Different users need different levels of control so work can be created quickly, executed safely, and closed with accountability.

Overview

In SolarSENS, permissions are not only about access. They define who can move work through key decision points such as assignment, resolution review, unarchive, and deletion.

This matters because work orders often involve customer-facing commitments, site visits, safety implications, and performance impact. The platform separates execution from approval so teams can maintain discipline without slowing down work.

Why it matters

It prevents the same person from both doing and approving work without oversight.
It protects historical records from accidental deletion or uncontrolled edits.
It gives supervisors a clear review queue instead of relying on manual follow-up.
It helps customers understand who is responsible at each stage of the workflow.

How it works in SolarSENS

Operators and coordinators

Operators and coordinators typically create work, monitor queues, add context, and keep issues moving. They are often the first people to translate alarms, plant findings, or customer requests into a formal work order.

Supervisors and admins

Supervisor and admin roles usually control the management actions that change the official state of a work order. In WorkOrder V3, that includes actions such as assignment, resolution, approval, rejection for rework, queue-level review, and delete-request decisions.

These roles also have access to the review-oriented and analytics views used to manage backlog and closure quality.

Assigned technicians or executors

Assigned technicians or executors are responsible for carrying out the field or desk action required by the work order. They may not approve their own work, but they remain central to execution because they provide the notes, evidence, and updates that allow reviewers to decide whether the issue is truly resolved.

When a reviewer sends a work order back as Action Needed, the assigned technician can revise the work and submit it again for review.

Delete governance

Deletion is treated differently from normal editing. Direct deletion is reserved for supervisor or admin level control. Users without those permissions can still request deletion, creating a reviewable queue instead of silently removing records.

Practical model to use

When documenting or operating WorkOrder V3, think in terms of four responsibilities:

create the work
own the work
review the work
govern historical records

One person can hold more than one responsibility, but the workflow is strongest when review and governance stay controlled.