Differences

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

Link to this comparison view

Both sides previous revision Previous revision
cms:users:props [12/07/2018 12:24]
tagr WH-129
cms:users:props [24/09/2018 10:41] (current)
tagr
Line 14: Line 14:
  
 **Password**\\ **Password**\\
-Password ​is required for each user. +A password ​is required for each user. 
 To ensure a high quality of password protection, it is recommended to adhere to the following rules when creating it: To ensure a high quality of password protection, it is recommended to adhere to the following rules when creating it:
   * the minimum password length is 4 characters;   * the minimum password length is 4 characters;
Line 23: Line 23:
  
 **Host mask**\\ **Host mask**\\
-The host mask can be applied to the user to restrict IP addresses from which this user can log on to the system (for example, to restrict access only to working computers). To set a mask, use the wildcard character *, for example, the host mask can be set like this: //​212.0.13.*//​. You can indicate several masks separated by commas. The maximum number of symbols in this field is 1024. If no mask is set, the user can log in from any computer. ​+The hostmask ​can be applied to the user to restrict IP addresses from which this user can log on to the system (for example, to restrict access only to working computers). To set a mask, use the wildcard character *, for example, the hostmask ​can be set like this: //​212.0.13.*//​. You can indicate several masks separated by commas. The maximum number of symbols in this field is 1024. If no mask is set, the user can log in from any computer. ​
  
 **Creator**\\ **Creator**\\
-Select the creator from the dropdown list. User's [[cms/​rights/​rights#​creator|creator]] can be any other user. Creator ​is important to build hierarchy of the access rights. The user inherits account and billing plan from the creator. The creator is assigned when the user is being created and cannot be changed afterwards.+Select the creator from the dropdown list. User's [[cms/​rights/​rights#​creator|creator]] can be any other user. The creator ​is important to build the hierarchy of the access rights. The user inherits account and billing plan from the creator. The creator is assigned when the user is being created and cannot be changed afterwards.
  
 **Account**\\ **Account**\\
Line 38: Line 38:
  
 **Can change password**\\ **Can change password**\\
-Allow/​forbid the user to change the password. If this option is enabled, then, according to the security rules, the  user will be required to [[user/​gui/​login?&#​password_change|change the password]] at the first login.+Allow/​forbid the user to change the password. If this option is enabled, then, according to the security rules, the user will be required to [[user/​gui/​login?&#​password_change|change the password]] at the first login.
  
 **Can send SMS**\\ **Can send SMS**\\
Line 44: Line 44:
  
 **Enabled**\\ **Enabled**\\
-If disabled, the user cannot ​login to any interface of the system. ​+If disabled, the user cannot ​log in to any interface of the system. ​
  
 **Can change settings**\\ **Can change settings**\\
Line 65: Line 65:
 {{ :​users:​access.png?​nolink }} {{ :​users:​access.png?​nolink }}
  
-Note that here you set the rights of a specific user to various objects of the system. However, the user, in turn, is also a system object and therefore can be accessed by other users. In other words, other users can obtain access rights toward this user. To set access to a user as a system object, open the properties dialog of some other user and choose //Users// in the dropdown ​filter. ​+Note that here you set the rights of a specific user to various objects of the system. However, the user, in turn, is also a system object and therefore can be accessed by other users. In other words, other users can obtain access rights toward this user. To set access to a user as a system object, open the properties dialog of some other user and choose //Users// in the drop-down ​filter. ​
  
 ===== Advanced ===== ===== Advanced =====
Line 85: Line 85:
 :!: Access required: //View custom fields// — to view general custom fields; //Manage custom fields// — to create, edit, and delete general custom fields for the given unit; //View admin fields// — administrative custom fields; //Manage admin fields// — to create, edit, and delete administrative fields. ​ :!: Access required: //View custom fields// — to view general custom fields; //Manage custom fields// — to create, edit, and delete general custom fields for the given unit; //View admin fields// — administrative custom fields; //Manage admin fields// — to create, edit, and delete administrative fields. ​
  
-On this tab, you can add any information about the user, whether it is home address or working shift. In the left field enter the name of the field, in the right field its value. To save a custom field, click the //Add// button, to delete — //Delete//. At the end of the dialog edit, click //OK// in the lower right corner. The next time you open the dialog, the fields will be automatically sorted alphabetically. Part of the fields can be marked as //​administrative//​ (checkbox in front of the field), i.e. they will only be visible to users with the appropriate rights.+On this tab, you can add any information about the user, whether it is home address or working shift. In the left field enter the name of the field, in the right field its value. To save a custom field, click the //Add// button, to delete — //Delete//. At the end of the dialog edit, click //OK// in the lower right corner. The next time you open the dialog, the fields will be automatically sorted alphabetically. Part of the fields can be marked as //​administrative//​ (checkbox in front of the field), i.e. they will only be visible to users with the appropriate rights.
  
 {{ :​users:​fields.png?​nolink }} {{ :​users:​fields.png?​nolink }}
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam