Role Permissions Explained
A detailed matrix of what each role can view, create, edit, and delete across all features.
Permission Structure
Every feature in JobLine.ai has four permission levels: View (read-only access), Create (ability to add new records), Edit (ability to modify existing records), and Delete (ability to remove records). Each role is granted a specific combination of these permissions for each feature. Permissions are enforced both in the user interface (buttons are hidden or disabled) and at the database level (API calls are rejected if the user lacks permission).
Work Orders
Viewers and Operators can view work orders within their team scope. Operators can also update parts counts and status for orders at their station. Supervisors can create, edit, and reassign work orders within their team. Admins can do all of the above across all teams, plus delete work orders (a rare action typically reserved for correcting data entry mistakes).
Handoffs
Operators can view handoffs at their station and create new ones. They cannot delete handoffs (to preserve the audit trail). Supervisors can view all handoffs within their team, create handoffs, and acknowledge them on behalf of absent operators. Admins have full access across all teams.
NCRs (Non-Conformance Reports)
Operators can view NCRs and file new ones. Only Supervisors and above can disposition NCRs (approve, reject, set rework/scrap). Admins can modify and close NCRs across all teams. No role can delete an NCR — they are permanent quality records.
Stations and Equipment
Operators can view station details and check in/out. Supervisors can create and configure stations within their team. Admins can manage stations across all teams, including setting up work center types and attaching machine profiles.
Users and Settings
Only Org Admins can manage user roles, organization settings, billing, ERP connections, and the part catalog. Supervisors can invite new members to their team but cannot change roles or access billing. Operators and Viewers have no access to administrative functions.
Data Scope Enforcement
Beyond action-level permissions, data visibility is scoped by team. An Operator on Team A cannot see Team B's work orders, even if both teams belong to the same organization. Supervisors see all data within their assigned team(s). Admins see all data across all teams. This scoping is enforced at the database level using row-level security, meaning it cannot be bypassed even through direct API calls.