2.09 User Management

Last modified by Wecon on 2025/12/10 11:44

2.9 User Management

User management is divided into "account management, role management, and group management" functions, which are mainly used for adding and editing sub-accounts, as well as allocating sub-account permissions and devices.

In user management, different management roles can be set according to different permissions, and different roles can be assigned to each user account.

Step description:

Step 1: Create a "group"(if there is a default group, this step can be ignored)
Step 2: Create a "role"
Step 3: Create an "account"

2.9.1 Account management

2.9.1.1 Create account

On the [Account management] page → click the [+Create account] button to create a sub-account of the current account, as shown in the figure below.

Note:

Username: The name of the account you are creating. The username is 1-20 characters long and can only consist of letters, numbers, and underscores.
Password: User password. The password length cannot be less than 6 characters. (If the strong password mode is enabled, the password length must be no less than 8 characters and must contain uppercase and lowercase letters, numbers, and special symbols.)
Roles and groups: Before creating an account, please configure the role in [Role management].
Nickname: Configure a nickname for the account.
Enable: Checking Enable means that the account can log in normally. Unchecking it prohibits login.
Assign: After enabling, group operations are disabled.

2.9.1.2 View the role permissions of an account

Click the role name in Account Management to view the "Function Permissions and Device Permissions" of the role, as shown in the figure below.

2.9.1.3 Assign/Unbind Devices

(1) Assign devices

Click the [Assignment device] buttonto view the list of devices assigned to the sub-account, click the [+Assign device] button, select the V-Box/IoT HMI to be assigned to the account in the pop-up box, and click the [OK] button to assign the V-Box/IoT HMI to the account, as shown in the figure below.

Information

The current account can only assign V-Box/IoT HMI to the sub-accounts created by itself. For all subordinate sub-accounts created by the sub-account, it can only browse the list of allocated V-Box/IoT HMIs.

(2) Unbind devices

In the list of assigned V-Box/IoT HMI, you can unbind the selected V-Box/IoT HMI from the account by clicking the [Unbind] button or the [Unbind in batch] button. After unbinding a V-Box/IoT HMI of a sub-account, the V-Box/IoT HMI devices assigned to all subordinate sub-accounts will also be unbound, as shown in the figure below.

2.9.1.4 Role account level

The created account will be displayed in the account management list. The following is a complete five-level account diagram. The current account is the administrator account (first-level account), and the interface is as shown below.

Note:

①Account can create a "role" and configure permissions for the "role". After a sub-account is associated with the "role", it is granted the corresponding permissions of the "role".

②If an account disables a certain permission of a "role", the permissions of its sub-accounts and sub-accounts of sub-accounts will all follow.

(For example: if the management account disables the real-time data configuration permission of a "role", all its sub-accounts, sub-sub-accounts... will no longer have this permission)

③If an account enables a certain permission of a "role", it will only affect the sub-accounts of the account.

(For example: if the management account enables the real-time history data configuration permission for a "role", all second-level sub-accounts under it will turn on the permission, but the sub-accounts... will still be disabled and must be enabled by the sub-account of the management account)

④Account can assign a gateway or IoT HMI to a sub-account. All gateways or IoT HMIs obtained by the sub-account will follow the permissions of the corresponding role of the sub-account.

⑤If an account unbinds the gateway or IoT HMI assigned to its sub-account, it will also unbind the gateway or IoT HMI assigned to all sub-accounts...

⑥If an account disables a sub-account, its sub-accounts will also be disabled.

⑦If an account enables a sub-account, it will only affect the current sub-account, and its sub-accounts will still be disabled and must be enabled by its sub-account.

2.9.2 Role management

Role management can "add" role configuration, "edit" permission configuration, "configuration" HMI/V-Box permissions, and "delete" role permissions.

2.9.2.1 Add role

In [Role management], click [Add] and check the permissions you need in the corresponding places. By checking the "Permission Configuration" of the role, you can control the permissions of the account corresponding to the role, as shown in the figure below.

The sub-account permissions will be different depending on the "Permission Configuration" selected by the administrator.

Noted:

①It is not possible to configure the permissions of "add device, unbind device, replace, transfer and V-Box points" for the sub-account.

②"Fourth-level sub-account" cannot configure user management permissions for "fifth-level account".

③"Menu" and "Button type" are not strongly related. The gray area is "button". Select any button to check the parent level. If the parent level is checked, the corresponding buttons will not be checked. You need to check them manually. Just check the permissions you need in the corresponding places, as shown in the figure below.

2.9.2.2 Configure device permissions

Click the [Configure] button to configure the "V-BOX permission and HMI permission" of the account corresponding to the role. After configuring the role's permissions, click the [Save Settings] button to save the modified role permissions, as shown in the figure below.

In the permission configuration, move the mouse to the iconbehind the configuration item to view the description of each permission.

2.9.2.4 Delete role

If you want to delete a role, you need to determine whether the role is bound to a role. If it is bound to a role, you need to unbind the association between the account and the role before you can delete the role.