About command-level security for menu commands and buttons

Window, menu, and field- level security enable you to limit access to specific windows and fields in a window. However, this type of security alone does not prevent a user with access to a window from using certain commands and buttons to view sensitive information in related windows.

If you want to provide access to certain users to enter information in a window, while preventing them from viewing sensitive information in related windows, you need to use command-level security. Similar to field-level security, you turn on command-level security using the F7 key. Command-level security is available for Options and Post menu commands in several Sage 100 Contractor windows.

Where security is available for an Options menu or Post menu command or for a corresponding button, you click the command on the menu, and then press the F7 key to open the Security window for that command. You use the Security window to allow access to different types of users. For example, in the 1-4 Recurring Transactions window, select Post > Multiple Transactions, press F7, and then select the checkbox beside each security group that can post recurring transactions. Clearing all the checkboxes removes the security for the command.

Note: Only Options menu and Post menu commands that do not already require administrative rights provide this command-level security.

Viewing security settings

In windows that have a View menu, you can view the fields and commands to which access is restricted in that window.

When you click View > Security, the program highlights the fields and commands for which security is turned on. In this View Security mode, you cannot edit any of the fields in the window, although you can still turn security off and on.

Security reports

Print the 13-7-23 Security Settings report to view the security group that have access to menu commands and buttons. You can run this report for users and for security groups.

You can also view command-level security settings on the 13-7-22 Database Security/User Def report.