Role-based access on iNut PC for SCADA

A SCADA system needs separate view, control, and configuration rights so each operating group can do only its assigned work.

Request an architecture review Read the access-control note

Source cover for role-based access on iNut PC — The owner approved an anonymous contract-evidence scope; public copy covers the permission matrix and acceptance method without a production KPI.

SYSTEM PATH

Architecture described by the public source

MQTT ClientID -> iNut PC -> Admin / Operations / Supervisor roles -> View / Control / Config permissions.

Problem: A SCADA system needs separate view, control, and configuration rights so each operating group can do only its assigned work.
Architecture: MQTT ClientID -> iNut PC -> Admin / Operations / Supervisor roles -> View / Control / Config permissions.
Deployed layer: iNut PC · mqtt_clientid · three operating roles · view/control/config permissions
Described outcome: Turn access control into an inspectable configuration instead of sharing one account across operating shifts.

EVIDENCE BOUNDARY

Approved evidence boundary

This dossier separates the public technical description from the owner-approved scope in the worksheet. The status permits anonymous source evidence only; customer names, KPIs, field photos, and endorsements need separate permission.

Read the access-control note Explore all dossiers