Page access
A page can be limited to signed-in users and to certain profiles, for example an engineering page that only maintenance staff should open. The setting is on the page in the screen editor and applies on the run screen.
The setting
In the screen editor, select the page (click an empty place on the canvas). In PROPERTIES, the group Access has:
- Login Required: only signed-in users may open the page. Off by default for new pages.
- One check box per profile: if none is ticked, every signed-in user may open the page; otherwise only users with at least one of the ticked profiles.
The group is shown only when user login is on for the project; see Turn on authentication.
What the operator sees
| Situation | Result |
|---|---|
| Not signed in, page needs login | The sign-in window opens; after signing in the page opens |
| Signed in, profile not allowed | The page does not open; the screen stays on the current page. In the Run mode of the editor a message says You do not have access to this page. |
| A page embedded in another page with the Page iframe object | A lock with You are not allowed to view this page |
Navigation buttons, click actions and scripts all go through the same check. Root opens every page, whatever profiles are ticked.
What page access is for
Page access keeps operators away from pages they do not need. It does not keep information secret.
What protects the plant are the server-side checks of every action: permissions for commands and settings, responsibility zones for control, interlocks and approvals. A user who opens a page without access to it still cannot send a command that their profile does not allow.
Do not put information on a page that some signed-in users must not see; if needed, run a separate project for them.