Accessing user has one or more groups in common with local (logged on) user You can use this condition to specify that the accessing and the local user have to be members of at least one common group, for example a user group for a class or a seminar. This access is necessary for the Veyon Master to execute specific functions via the Veyon Service (e.g.

This ensures for example that teachers can access the local Veyon Service. Accessing computer is localhost If this condition is enabled, the rule applies only if the accessing computer is the local computer. This can for example be used to prevent teachers from accessing computers in different classroom. Accessing computer and local computer are at the same location With this condition you can determine that the accessing computer and the local computer have to be located at the same location. If no or only wrong locations are selectable the Network object directory has to be adjusted. Computer is located at With this condition you can define that either the accessing or the local computer has to be located at a specific location. If no or only wrong groups are selectable, the User groups backend under the general settings for Computer access control may have to be adjusted. User is member of group With this condition you can define that either the accessing or the locally logged on user must be a member of a specific group. If a condition is configured so that a user must be a member of a specific group, the rule only applies, if the said user is not a member of the group.įor a rule to be processed, one or more conditions must apply. For example, if the condition No user logged on is activated, the rule only applies if one or more users are logged on. You can use the Invert all conditions option to determine that all activated conditions are inverted before evaluation, meaning that activated conditions must not apply. This particularly useful for fallback rules at the bottom of the rules list, where you can specify that the logged on user is asked for permission if no other rules apply. The option Always process rule and ignore conditions causes the conditions set below not to be examined for rule processing and the set action is always executed. For documentation purposes an optional description can be added to the Rule description input field. The name is later used to identify the rule and is displayed in the rules list. A name for the rule should be defined in input field Rule name first.

Lanschool lite download