User administrationMenu Project – User administration.
With the user administration one or more users are assigned to a page of the visualization. Through the control element Block user control you log in on the APP and afterwards only see those pages that are released for this user.
In the dialog users are created with + and removed again with −. For each entry a user name and a password are given. The user name is stored in the project, the password on the other hand in the persistent values of the controller – because it can also be changed at the control element and must not be overwritten again on the next transfer.
The user name must not contain # or ;. The password must not be empty and must not contain #. Other entries are rejected with a message.
Optionally, an icon can be assigned to each user: right-click the user – Select icon.... The selection of the project graphics opens, the same one the control element Dynamic graphic uses. With Remove icon the user returns to the default icon. The icon is shown in front of the name in the list and by the Block user control for the logged-on user. If none is selected, the default icon is shown. A graphic that is only used as a user icon counts as in use in the image selection.
In the page tree you define which users may see a page. The assignment is maintained only here, the properties of the page no longer contain a setting for it. Users already assigned in existing projects are kept.
If a user is renamed or deleted, the change is carried over to the page assignments. Note: if a page has no user left afterwards, it is visible to everyone again. The tree only contains visualization pages, no program pages.
The users that may access a page are selected in the dialog (see above). The following applies:
The login page is linked to no user. The exact order of the search is described under Start page.
New design: There the assignment always applies; the setting Respect user rights of the controls is hidden. A page assigned to another user can be opened neither by tapping nor by swiping; swiping skips it. Pages with no user stay reachable for everyone, even without logging in. Every page that is to be protected must therefore be linked to a user, not only the start page. Exceptions are a page jump after entering a PIN and a jump via an address, for example to an alarm page. To prevent swiping from a page altogether, use Lock swiping to other pages in the page properties.
Tip: If the APP is to start with a certain user right away without logging in, there is the start parameter --logon-user, see APP – Start parameters.
Note: If a fixed start page is also set in the project, it takes precedence over the page of the user after logging in. It is shown to everyone, even without logging in and without an assignment. How the start page is determined is described under Start page.