User permissions and groups

<< Click to Display Table of Contents >>

Navigation:  Introduction > !MC5 remote control > Client/Server >

User permissions and groups

Which users have access to which data via the client is controlled via user groups, among other things. When sending files, the groups can also be used to control to which partners a particular user can send them (for more information on user groups, see Users and groups).

 

Incoming data

Received data is checked as follows and made available to the clients accordingly. This is done in the specified order. Only the first matching equivalent is used for forwarding!

 

(ENGDAT only) Check forwarding address for user ID - If ENGDAT data is received, the system first checks for the existence of a forwarding address in the ENGDAT header file (defined in VDA guideline 4900 as field S0003-0014 in block UNB). If one exists, then it is checked whether a user exists whose user ID corresponds to the specified value. If this is the case, the file input is forwarded to this user and no further checks and forwardings are made.

(ENGDAT only) Check forwarding address for group ID - If a forwarding address was specified but no matching user was found, the next step is to check whether a user group with a corresponding group ID exists. If this is the case, the file inbox will be forwarded to all users that belong to this group. After that, no further checks or forwarding will be performed.

Note

Specifying a group ID as the forwarding address is generally preferable to using a user ID. This way, multiple users can always be notified of a file receipt, and control over which users receive notifications can be done locally without having to customize the forwarding address on the partner side.

Check for user groups assigned to the partner - If no match has been found so far, or if the incoming file was not received in ENGDAT format, the system checks whether user groups have been assigned for the corresponding partner in the partner settings under Special functions (see Special functions). If this is the case, the incoming file is forwarded to all users that belong to one of these groups. After that, no further checks or forwarding will be performed.

User right Users receive unassigned inputs - All inputs that could not be assigned at this point will be forwarded to all those users who belong to a group where the option Users receive unassigned inputs is activated (see Create/edit a user group). If no corresponding user is found, then the file input will not be reported to any client.

 

Outgoing Data

In the outgoing direction, you can restrict which partners are displayed for the clients and thus to which partners data can be sent. To do this, the users must be assigned to a group for which the option Users see only a limited partner selection is activated (see Create/edit a user group). This means that all partners are initially "invisible" for this user. To make a certain partner "visible", the corresponding group must now be assigned to this partner in the partner administration under Special functions / Groups Client/Server (see Special functions).

 

The visibility or non-visibility of a partner has no influence on the display of received data if this is forwarded to a specific user via the forwarding address!