Viewer Readonly Overview
Understand what the portal looks and behaves like for a user with the Viewer (read-only) role: you can browse and inspect, but create / edit / delete controls are disabled.
Before you start
Section titled “Before you start”- Prerequisites: An account with the Viewer role in the active organization.
- Required role/permission: Viewer — explicitly not an Admin/Editor.
- Settings that affect behavior:
- Role / group assignment — the role (or group membership under
/portal/security/groups) is exactly what makes the experience read-only. Changing the role changes what is enabled. - Project access — even with a higher org role, per-project access can still restrict editing of a specific project (see Project access).
- Active organization — your role can differ per organization; switching org may change what you can do.
- Role / group assignment — the role (or group membership under
- Sign in with the Viewer account (see Sign in).
- Open Overview (
/portal/overview) and navigate the sections — projects, devices, licensing, analytics — all are viewable. - Notice that Create / Add, Edit, and Delete actions are hidden or disabled across screens (e.g. Users, Devices, Projects).
- Open a project in the IDE (
/portal/workspace/ide/:id): you can read the code and HMI, but editing/saving is blocked. - Runtime controls (start/stop/deploy/delete) are unavailable; you can still view status (see Runtime control overview).
No captured steps yet. Run make regenerate-flows after a portal-e2e:docflow pipeline run produces docflow-output/viewer-readonly-overview.json.