User Tools

Site Tools


managing_users

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
managing_users [2021/11/24 11:11]
emozolyak [Guest user]
managing_users [2022/01/18 20:25] (current)
127.0.0.1 ↷ Links adapted because of a move operation
Line 1: Line 1:
-{{  :menu-icon-users.png?nolink&60}}+{{  network:menu-icon-users.png?nolink&60}}
 ====== Managing users ====== ====== Managing users ======
  
Line 6: Line 6:
  
 In WebHMI, there is a mechanism for managing users and their roles. The roles give or forbid access to certain project parts, while the users are binded to these roles. In WebHMI, there is a mechanism for managing users and their roles. The roles give or forbid access to certain project parts, while the users are binded to these roles.
-{{ ::user_roles.png?direct&600 |}}+{{ network:user_roles.png?direct&600 |}}
  
 You can access the user setup from pop-up menu (for 3.6 and higer fw) You can access the user setup from pop-up menu (for 3.6 and higer fw)
-{{ :setup_menu_newest_users_entry.png?nolink |}}+{{ network:setup_menu_newest_users_entry.png?nolink |}}
  
 Or from the side menu (for 3.5 and lowe fw) Or from the side menu (for 3.5 and lowe fw)
  
-{{ ::setup_users_new.png?direct&800 }}+{{ network:setup_users_new.png?direct&800 }}
  
  
Line 20: Line 20:
 On a new device, there are 3 roles configured by default: On a new device, there are 3 roles configured by default:
  
-{{ ::roles_list.png?direct&500 |}}+{{ network:roles_list.png?direct&500 |}}
  
 === Admin role === === Admin role ===
Line 27: Line 27:
 <wrap em> This role with id = 1 can not be deleted from the project and only one property can be changed - its title.  </wrap> <wrap em> This role with id = 1 can not be deleted from the project and only one property can be changed - its title.  </wrap>
  
-{{ ::edit_admin_role.png?direct&400 |}}+{{ network:edit_admin_role.png?direct&400 |}}
  
 === Other roles === === Other roles ===
Line 38: Line 38:
 == Role configuratin page == == Role configuratin page ==
  
-{{ ::role_edit_example.png?direct&300 |}}+{{ network:role_edit_example.png?direct&300 |}}
  
 ===== Managing users ===== ===== Managing users =====
 <wrap em> As in case with the roles, there is a static "admin" user with id = 1 who can not be deleted. Only these attributes for him can be changed: </wrap> <wrap em> As in case with the roles, there is a static "admin" user with id = 1 who can not be deleted. Only these attributes for him can be changed: </wrap>
  
-{{ ::admin-1_edit_possibilites.png?direct&600 }}+{{ network:admin-1_edit_possibilites.png?direct&600 }}
 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. 
  
Line 53: Line 53:
   * other similar scenarios   * other similar scenarios
  
-{{ ::guest_page_.png?direct&800 |}}+{{ network:guest_page_.png?direct&800 |}}
  
 Then, the login page for the users will look like: Then, the login page for the users will look like:
  
-{{ ::guest_login.png?direct&400 |}}+{{ network:guest_login.png?direct&400 |}}
  
 Click //Login into system// for standard login page. Click //Login into system// for standard login page.
Line 66: Line 66:
 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. 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.
  
-{{ ::user_idle_setting.png?direct&600 |}}+{{ network:user_idle_setting.png?direct&600 |}}