VTS enables you to specify a set of custom application privileges that will automatically be loaded for users who are not logged on to your application. These application privileges will also be automatically granted to newly-created user accounts.
The AppPrivDefault SecurityManager.ini variable enables you to do so by turning on those security bits related to each custom application privilege you've created for your application.
As with the SysPrivDefault variable (see Establish Default System Privileges for an Application, you can set the appropriate bits to "1" to make them default application privileges; however, the bits are relative to the custom application privileges you've added to your application.
For example, if you've added 4 custom application privileges to your application (as exemplified below), and you wish to allow non-logged on users and new users access to the first two only, you would set the first two bits to "1" (from left to right) as follows:
[SECURITYMANAGER-PrivApp]
PrivBitsTotal = 4
AppPrivDefault = 1100
PrivDesc0 = Access Pump Controls
PrivDesc1 = Control Pumps
PrivDesc2 = Access Motor Controls
PrivDesc3 = Control Motors
The result of the above configuration is that by default, users who are not logged on, and users with newly-created accounts will be able to access pump controls and control the pumps for your system, but will not be permitted to access or control motors.
VTS also gives you the ability to define any system privileges that you wish to be granted to users who are not logged on to your application, and to newly-created user accounts. Instructions are provided in Establish Default System Privileges for an Application.