1.Introduction
The HS/FS offers the option of managing user groups.
16 user groups are available for menu operation (Menu, Query, Visualisation). A further 16 user groups are available for access to lists.
Access rights are assigned or revoked via the user groups. All user groups have the same status, there are no gradations within the user groups. The groups can be assigned names under Master data\Project\Project settings\Other\User groups. For access to menu operation, a distinction can be made between "display/read" and "execute" (see Master data\User, User rights tab). Only "access rights" are assigned for lists.
To ensure that a user has access rights to the menu or lists, he/she must be assigned to these groups. There are corresponding masks (see below) in the user master for this.
Corresponding masks are available in the menu and for the lists and HS/FS objects for assigning the user groups.
To ensure access later in the HS/FS, the user must be assigned to at least one user group which was also assigned to the respective element. Figuratively speaking, you can say that the lists (of user groups and HS/FS element) are laid over each other. Access is possible if at least there is one match.
16 user groups are available for menu operation (Menu, Query, Visualisation). A further 16 user groups are available for access to lists.
Access rights are assigned or revoked via the user groups. All user groups have the same status, there are no gradations within the user groups. The groups can be assigned names under Master data\Project\Project settings\Other\User groups. For access to menu operation, a distinction can be made between "display/read" and "execute" (see Master data\User, User rights tab). Only "access rights" are assigned for lists.
To ensure that a user has access rights to the menu or lists, he/she must be assigned to these groups. There are corresponding masks (see below) in the user master for this.
Corresponding masks are available in the menu and for the lists and HS/FS objects for assigning the user groups.
To ensure access later in the HS/FS, the user must be assigned to at least one user group which was also assigned to the respective element. Figuratively speaking, you can say that the lists (of user groups and HS/FS element) are laid over each other. Access is possible if at least there is one match.
2.Menu items are to be hidden
Example with 3 users - a maintenance department
The boss is allowed to see all the menu items (belongs to user group 1)
The electrician is only allowed to see the menu items for electrics (belongs to user group 2)
The installer is only allowed to see the menu items for heating (belongs to user group 3)
The boss is allowed to see all the menu items (belongs to user group 1)
The electrician is only allowed to see the menu items for electrics (belongs to user group 2)
The installer is only allowed to see the menu items for heating (belongs to user group 3)
| User belongs to | user group Read | user group Execute |
|---|---|---|
| Boss | 1,2,3 | 1,2,3 |
| Electrician | 2 | 2 |
| Installer | 3 | 3 |
| Menu level 1 | Menu level 2 | user group Read | user group Execute |
|---|---|---|---|
| Room 1 | - | 1,2,3 | 1,2,3 |
| Dimmer 1 dimming value | 1.2 | 1.2 | |
| Dimmer 1 Status overload | 1.2 | 1.2 | |
| Room temperature | 1.3 | 1.3 | |
| Status Indoor fan | 1.3 | 1.3 |
3.Lists
Separate access rights can be assigned for lists.
The general access rights to lists are assigned under Master data\User in the User rights tab and there in the Lists subtab. Marked groups are assigned reading rights.
Example: One archive per HTTP call is to be made accessible for different user groups. For this, an entry must be created under Archives and Lists\Archives in the HTTP call tab of the respective archive. The reading rights now have to be assigned to the authorised groups by marking under the mask item User groups.
The general access rights to lists are assigned under Master data\User in the User rights tab and there in the Lists subtab. Marked groups are assigned reading rights.
Example: One archive per HTTP call is to be made accessible for different user groups. For this, an entry must be created under Archives and Lists\Archives in the HTTP call tab of the respective archive. The reading rights now have to be assigned to the authorised groups by marking under the mask item User groups.
4.End points
Separate access rights can be assigned for end points, whereby only reading rights can be assigned for some end points and reading and writing rights (separate from one another) for others.
The general access rights to end points are assigned under Master data\User in the User rights tab and there in the End points subtab. Marked groups are assigned reading or writing rights.
The general access rights to end points are assigned under Master data\User in the User rights tab and there in the End points subtab. Marked groups are assigned reading or writing rights.