managing_users
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
managing_users [2022/01/18 20:25] – ↷ Links adapted because of a move operation 127.0.0.1 | managing_users [2023/04/25 13:30] (current) – [Attaching roles to users] emozolyak | ||
---|---|---|---|
Line 45: | Line 45: | ||
{{ network: | {{ network: | ||
Admin can add as many roles and users as needed in your project. | Admin can add as many roles and users as needed in your project. | ||
+ | |||
+ | ==== Attaching roles to users ==== | ||
+ | |||
+ | When editing user properties, the roles which users use are in the list's top: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The other optoins will be described further: | ||
+ | |||
+ | === Screencast mode === | ||
+ | |||
+ | In this mode, the page which is the logged in user will see, can be set via the URL link written to dedicated register in the system. More on this in this [[screencast|article]] | ||
+ | |||
+ | === Disable menu use === | ||
+ | The user won't be able to access the side bar and setup menu neither via hot key (~) nor via interface navigation elements. You should provide link to the necessary project parts right in your project. | ||
+ | |||
+ | === Use server time === | ||
+ | The pages WebHMI' | ||
+ | |||
+ | === Add Registers to the side menu === | ||
+ | The // | ||
+ | |||
+ | === Home page === | ||
+ | |||
+ | This is a page user land when he logs in. Please check the user's role allows the user to access this page, otherwise he won't be able to enter. | ||
+ | |||
+ | === Auto close unattended user session === | ||
+ | When working in a “multitasking” mode, most users open and leave “for ever” a lot of open tabs at the same time – this is more practical than constantly opening and closing the same tab. They are often opened from different devices. However, the system continues to exchange data with the browser, even if the user does not look at the page for several days. This subtle “trickle” can become a “stream” in a multiuser system, and also create unnecessary load on the system. | ||
+ | |||
+ | Now, in the user settings, you can set an idle timeout after which the exchange of data with the page will automatically stop and resume after the page is refreshed. | ||
+ | |||
+ | {{ network: | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
===== Guest user ===== | ===== Guest user ===== | ||
Line 61: | Line 101: | ||
Click //Login into system// for standard login page. | Click //Login into system// for standard login page. | ||
- | ==== Auto close unattended user session ==== | ||
- | When working in a “multitasking” mode, most users open and leave “for ever” a lot of open tabs at the same time – this is more practical than constantly opening and closing the same tab. They are often opened from different devices. However, the system continues to exchange data with the browser, even if the user does not look at the page for several days. This subtle “trickle” can become a “stream” in a multiuser system, and also create unnecessary load on the system. | ||
- | Now, in the user settings, you can set an idle timeout after which the exchange of data with the page will automatically stop and resume after the page is refreshed. | ||
- | |||
- | {{ network: | ||
managing_users.1642537551.txt.gz · Last modified: 2022/01/18 20:25 by 127.0.0.1