Access Level Properties

The Access Level properties allow you to associate the objects with access and user levels so that only the users with the necessary rights can use them.

To edit the Access Level Properties, select the object with the mouse and use the Movicon 'Property Window'.

The Access Level properties are active only when the "Enable Password Manager" property from the 'Users and User Groups General Properties' has been in enabled in the project.

Write Access Level

This property is used to define the Access Level mask needed to execute, for example, the command list associated to the control. If the access level mask of the currently logged on user does not correspond to the control's settings, the user will not be allowed to execute any command operations associated to that control.

For further information, please refer to the paragraph on "User Levels and Access Levels".

Read Access Level

This property is used to define the Access Level mask needed for reading the control. If the access level mask of the currently logged on user does not correspond to the control's settings, the control will become invisible preventing the user from reading it.

For further information, please refer to the paragraph on "User Levels and Access Levels".

User Level

This property is used to define the User Password level needed, for example, to execute the commands associated to the control. When the control in question is used by a user, Movicon will ask the user for a User Password level equal to or higher than the one set in the actual control. If the can satisfy this request and therefore has the necessary access rights, they will be authentically acknowledged and granted access. Otherwise they will not be granted access and will be prevented from performing the operations they requested.

For further information, please refer to the paragraph on "User Levels and Access Levels".

Level Segregation

This property is useful when needing to restrict the use of functions implemented in an object or symbol for a specific Project or Runtime User Password Level. In order for this to function, you will need to make sure that the Password Management is active, and segregration must be used for individual objects and symbols.

Lower or higher user password levels will not be accepted.

The Login operation using the Password Level Segregation will be interpreted as a classic User Login.

Single El. Sign. for Commands

The property explicitly requests a First Level User Login with a Password indicated in the "First El. Sign. Level" property. There is no need to have the project's Password Management active for the First El. Sign. Level request. When the User interacts with the Object in which the Variable is set, the Login request will be executed through a specific Login Window requesting the "First El. Sign. Level" as the User Password Level.
Once the level has been validated successfully, the operation will be logged in the System Log.

Double El. Sign. for Commands

This property explicitly requests a First and Second Level User Login with a Password Level indicated in the "First El. Sign. Level" and "Second El. Sign. Level" properties. The project's Password Managment does not need to be active for the Electronic Signature Level request. When the User interacts with the Object in which the Variable is set, the Login request will be executed through a specific Login Window initially requesting the "First El. Sign Level" and then the "Second El. Sign. Level" as the User Password Level.
Once each level has been validated successfully, each operation will be reported in the System Log by indicating the set value and the user who validated it.
In this case, the Double Validation Signature cannot be performed by the same User but by two different Users for which it is absolutely necessary.

The use of the "Single\ Double El. Signatures" set in the Variable is a way to perform Validation Levels in objects, such as Displays or On-Off buttons for example, that cannot be configured to perform it.

The Validation Level can also be used without using the "Password Management" for User Logins. Conversely, if the User Login is enabled, the Single or Double Validation will also be required in the event of Failed User Login.

Networking Client applications can use the Validation Level that has been set in the Variables. The Client asks the Server to validate the credentials being the Variables managed directly by the Server. This will mean that the Client Variable may change value (e.g. set to '1') if the Server Validation is successful and thus cause the Variable to also change on the Server side. If unsuccessful, the Variable on the Client side will return to its original value and the one on the Server side will remain as it is.
The operations executed by the Client are also recorded on the Server.