There are some issues to consider when you are developing the security for your application.

Operator error can be prevented by ensuring that all control objects (e.g. output tag drawing methods such as sliders, command buttons, or numeric data entry fields) are placed on pop-up dialogs, rather than directly on your application pages. Operators will therefore be required to first open a dialog and then click a button to control equipment. This process should help to prevent accidental output by making operators conscious of their actions.

Further, protect your control objects with application privileges, so only certain operators can use them. You might even consider providing double protection for control objects; protect your pages and pop-up control dialogs with one application privilege, while protecting your control objects (i.e. output and/or modem tags) with another application privilege. Operators must then be granted two application privileges in order to control a piece of equipment. This will limit the number of operators who will have access to controls and pages.

You might wish to add a user account specifically for your own use, with a unique username and password, and then delete the Manager1 account from the application. This will prevent operators from access to the default user account. Information on deleting a user account can be found in Delete Account Dialog.

As you've witnessed, it is easy to modify the settings of variables in your configuration files. This includes security variables. You might wish to protect your configuration files (including the SecurityManager.ini file) from modification once the application is complete. You can do this by hiding the files or by protecting them using Windows security features.