DTE Technical Support - Operator Security


	How do I set up my Systems Controller for complete access to all applications? This situation requires only a Master security record the each company. Each operator requires a master security record. If that's all that's defined, they have access to all menu selections of all installed applications. From that point, you define those applications or menu selections to exclude access, restrict functionality, or password protect. Back to top

	I have a group of operators all requiring the same type of extremely specific DTE access. Do I have to define each operator's security individually? No, because Class codes would be more efficient. You can associate like groups of operators with a classification (class) code. The class code is defined with a pound/number sign ( # ) as the first and fifth character and a three digit number in between for the Operator ID field. Restrictions for DTE application and menu access are then defined for the class code (such as #111#), not the operator ID. Down To Earth requires a master security record for each operator but within the master, the User class determines their security limits. Once the class code is assigned, any exceptions to the class code are defined for the individual Operator IDs. If you have more than one like-group of operators, define as many class codes as you need. Back to top

	How do I define the security so that Payroll application requires password for entry? Password protection can be defined for the whole application or menu selections. For the Operator/User class and company access, enter the application code (PR ) for the application field and "DTE_PR " as the menu entry code. (A password can be assigned for any application or menu selection.) Define the access for Payroll as "Yes" or "No" as needed for each function (Add, Change, Delete, or Look) and enter the password you want to define in the Password field. NOTE: For this same function in DTE v3.5, enter a blank value (spacebar/space) for the Application field in lieu of the application code. Back to top

	How can an operator change their password without having access to the System Manager application? By using the Password shortcut from the Operator window.* This shortcut is often missed as a "Field Maintenance" shortcut but is the easiest way for a user to change their own password. Use or click on the green Password field label to be prompted for your old password, the new password and a confirmation. * This option is only available for DTE v7 series. Back to top

	How is the Unique ID used within Down To Earth? The Unique ID (UID) has two functions, 1) temporary filename extension and 2) higherarchy of transaction security. 1) This three character field is used as the filename extension of temporary work files within Down To Earth, usually in the WRK directory. For example, the file generated when you print a report to screen, posting messages/log file, and sorting results file. 2) The first position of the three character field controls which user can proof and post other user's transactions. DTE compares your operator's UID to the UID in each record in the transaction file for inclusion on a proof list or to post. Only transactions entered with your UID or a UID whose first character has a greater ASCII decimal value , are included in your proof list or posting. Transactions entered with a unique ID that has the same first character as your UID (equal ASCII decimal value) are not included. For example, you have four operators with the Unique IDs of 0mj , 1sd , 1wr , and 2ts ... >> the operator's unique ID of 2ts sees only their own transactions. The ASCII value of the first position of the unique ID (2) has the highest value (050) and the lowest priority of the four. >> the operator's unique ID of 1sd sees and posts their own transactions plus those transactions entered by the UID 2ts . The ASCII value of the first position (1) of the UID 1sd is 049 which has priority over any higher ASCII value, in our example, 050. >> the operator ID's unique ID of 1wr sees their own transactions, those entered by the UID 2ts but not the transactions entered by 1sd . Even though the value of the first position of the UID is the same priority as 1sd , the complete unique ID is not the same. Therefore the transactions entered by UID 1sd cannot be seen or posted by UID 1wr . >> the operator's UID of 0mj sees transactions entered by all the operators in the example. The ASCII value of 048 gives the highest priority. Back to top