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 technical source documents the roles and permission matrix; account policy, logs, and final approval remain project-scoped.

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

Source-linked does not mean owner-approved

This dossier separates the public technical description from claims that still require acceptance metrics, field evidence, and owner permission. Use the original source to verify what is available today.

Read the access-control note Explore all dossiers