Use the Access control page of the Window ID Editor notebook to control users' ability to activate or modify the settings for the new window(s) that match the characteristics on the Window ID page.
The Window ID Editor access controls are similar to the access controls provided by the DeskMan/2 Workplace Shell Extensions. But, where the WPS Extensions control access to a wide variety of operations that can be performed on objects, the Editor controls access to activating windows and changing their settings.
The Editor uses the same access control objects as does the WPS Extensions, and can control access both through local passwords and through LAN-logon. You can use the Editor to create and modify access control objects, even when the WPS Extensions are not loaded or are not running.
You can assign access controls to a window through either the WPS Extensions or the Editor but, when both are assigned and enabled, the access controls assigned using WPS Extensions will be used.
right mouse button> in the container. The Editor will open a pop-up menu.
Each operation can be protected by a different access policy, and you can assign more than one policy to any operation. If you assign more than one access policy to an operation, order of assignment is important because the policy assigned first will be evaluated first, the policy assigned second will be evaluated second, and so on.
For example, if you want the window(s) to be automatically available when a user is logged on to the network, and also available by password when not logged on, be sure to assign the LAN-Controlled access policy first. Otherwise, the user will always be asked for the password before granting access to the operation.
DevTech recommends you refer to the Access Control section for information about creating and using access control objects