ATEasy allows you to categorize users into different privileges, and to enforce policies on what those privileges of users can do within the program. The privileges or the lack of them can prevent users from viewing or modifying or debugging the application code. The theory behind this is that different levels of users have different levels of responsibility, and different rôles to play in using the program. At the same time, users cannot be allowed to change settings that are outside their level of privilege. The privileges and the user name and password are stored inside a users file (ATEasy.usr) which is usually stored in the Windows System folder, or in a network server shared by multiple workstations and protected by providing Read access to certain Windows users that belong to non-ATEasy administrators and write access to Windows users that contain teh ATREasy administrators. The Users dialog can be used to create groups and users and assign privileges, it can also customize ATEasy to require logging in before getting inside ATEasy IDE .
The user groups built into ATEasy are:
Administrators
Driver Authors
System Authors
Program Authors
Testers
In addition, there is a Custom profile which the Administrator can use to define a special combination of privileges. Similar to the way privileges and users file is used by ATEasy, ATEasy application can use the users file to make users login before running the application, providing them different application specific privileges and customization. The test executive driver is a good example for this. See the Test Executive help file for more information about multiple users support. The test executive uses the AUsers class and the Users variables to access the users, privileges and the test executive customized setting (toolbar, menu etc) that is stored in the users file.