Beneath the User information is the Security Role, which is where the user can be assigned the Security Officer Role, Admin Role, or None. If a user is a Security Officer they will have access to laua - they can turn laua security off and on, work with laua user Profiles and security classes, and run laua reports. The Admin role was introduced to allow the Security Officer partial access to users set up on the system - consider the Admin Role a Sub - Security Officer who has restricted access to users in laua. If the Role assigned here is None, the user will have no access to laua. The Class Supervisor parameter set to Yes will allow the user access to others' jobs and print files if they are in the same user group and security class. Admin Class is used in conjunction with the Admin Role allowing partial access to laua users and security. The Security Class field is where you assign the appropriate laua security class to the user. Locale is used if a user needs the ability to view text in Lawson forms in a language other than US English. Resource Units is a concept that is only applicable if the environment is not using latm (Lawson's Transaction Manager) the higher the number of resource units a user has assigned here the more operating system resources the user will have allocated. In the Default section, the user has options for required fields, field display, productline (data area/ID), printer name and menu assignments. We will look at the Groups segment in the next process. To navigate through all of the fields in the user profile, use the arrow keys on the keyboard and the function keys available in the laua window. F4 Select will allow you to change a value in a field and the F1 Help key offers valuable help for each field. Click the Next page button to continue.