Factory OS Docs
Roles

Roles at a glance

The twelve app roles, what each can open and change, who works on the floor, and who signs what.

View as Markdown

Every person in Factory OS has two kinds of role. They are easy to mix up, so keep them apart.

  • Workspace role: owner, admin or member. It controls the workspace itself: inviting people, renaming it, transferring ownership. See Workspace owner and admin.
  • App role: one of twelve. It controls which factory modules you can open, which you can change, and your menus. This page and the role pages below describe the app roles.

Separately, each person is linked to a person (for example Production supervisor or QA manager) and an employee. The person decides which signed steps you can take. The employee decides which training you must have.

The twelve app roles

RoleDemo personPage
Org adminGrace Ooi, QA managerOrg admin
Managing directorLee Chong MingManaging director
Sales / officeNurul AinaSales
PurchasingLim Wei JiePurchasing
StoreFarah HanimStore
PlannerPriya Menon, planner. Hafiz Rosli, supervisor.Planner
TechnicianAhmad Faizal, technician. Kumar Selvam, operator.Technician
QC inspectorSiti RahmahQC inspector
QA / regulatoryJason Wong, QA engineerQA and regulatory
EngineeringDaniel TanEngineering
MaintenanceZulkifli HassanMaintenance
EHS officerNurul AiniEHS officer

Access matrix

Full means you can create, edit and take steps. View means you can read but not change. None hides the module: it does not appear. These are the defaults. The Org admin can change them for the whole organization under Settings > Roles & permissions, so your organization may differ.

Roles and permissions

One row per role, one column per module. Only the Org admin sees this screen.

Roles and permissions matrix with a row for each role and a column for each module
  1. One row per role. The Org admin row is locked to Full.
  2. Each cell sets Full, View or None for that role and module.
RoleSalesPurchasingInventoryProductionQualityEngineeringMaintenanceSettingsEHS
Org adminFullFullFullFullFullFullFullFullFull
Managing directorViewViewViewViewViewViewViewViewView
Sales / officeFullViewViewViewViewViewNoneNoneView
PurchasingViewFullViewNoneViewNoneNoneNoneView
StoreNoneViewFullViewViewNoneNoneNoneView
PlannerViewViewViewFullViewViewViewNoneView
TechnicianNoneNoneNoneFullNoneNoneNoneNoneView
QC inspectorNoneNoneViewViewFullViewNoneNoneView
QA / regulatoryViewViewViewViewFullViewViewNoneFull
EngineeringViewViewViewViewViewFullViewNoneView
MaintenanceNoneNoneViewViewNoneViewFullNoneFull
EHS officerNoneViewViewViewViewNoneViewNoneFull

Notes on the matrix:

  • Home, the apps launcher and My settings are open to everyone.
  • The Org admin row is locked at Full. It cannot be lowered.
  • Engineering has View on Purchasing so the engineer who signs project orders and progress claims can open the order.
  • Store has None on Sales but sees one Sales page, Packing & dispatch. The store keeper builds and loads the packs there. Sales confirms the dispatch.
  • Except for that page, a role never sees a module set to None, and an ISO standard that is switched off hides its records for everyone.

Who works on the floor

The machine tablet (Floor) and phone scan open for these roles: Org admin, Technician, QC inspector, QA / regulatory, Planner, Maintenance, Store and Engineering. Managing director, Sales, Purchasing and EHS officer work in the office screens only.

Who signs what

Access lets you open a step. Signing authority lets you complete a signed one. See Signatures, reasons and common refusals for the rules.

PersonSigns by default
Purchasing officerPurchase requisitions: Approve · e-sign. Supplier corrective actions and evaluations.
QA managerEngineering change notes, QMS objectives, documents and changes, management reviews, internal audit programme, trend reviews, recalls, record disposal, software validation, device history records, lot release, complaints, training records.
QA engineerCAPA, audit findings, gauges and calibration, process validation, nonconformance reports. Also any step that needs a QC inspector.
QC inspectorIncoming, in-process and outgoing inspection records, QC orders, retention samples.
Production supervisorLine clearance, label reconciliation, paper transcription, the machine register. The planner may sign the supervisor steps too.
Store keeperStock counts, movements, nonconforming stock, housekeeping, storage environment.
Process engineerProduction methods, process FMEA, bill of materials, process steps, moulds and device files.
EHS officerEnvironmental and safety records.
Managing directorManagement system scope and appointments.

A QA manager can sign anything a QA engineer or QC inspector can. A QA engineer can sign anything a QC inspector can. The Org admin has no extra standing: Grace Ooi signs as the QA manager because her person is the QA manager, not because she is Org admin.

Change who can open what

Only the Org admin changes the matrix. See Roles and permissions. Changing a person's signing authority means linking them to a different person in Settings > Users & invitations, or giving them a delegation window in Settings > Entities & access.

Next steps

Signatures, reasons and common refusalsWhy a button is disabled and what to do.

Was this page helpful?

On this page