Security Overview

Merchant Central can have each application, and many POS activities, secured. This means that the system may be set up so that only certain users can access and carry out certain functions.

The security methodology employed in Merchant Central is based around Users and Security Groups. A Security Group is simply a group, or level, that can undertake certain tasks, for example Administrators, Accounts, POS, Inventory, Auditors, and so on. A user is assigned to one or more Security Groups, for example one user might only be in the POS group while another user is in the Accounts and POS groups. You then have the option of securing specific access in the system to Security Groups, for example the Accounts security group is allowed to run the Account function, therefore any user in the Accounts group is allowed to run the Account function.

If no security groups have been assigned to a security option, the system will assume that anyone is allowed to access that option. For this reason, it is recommended that you have a security group called Not Used which no users are assigned to. You can then assign this security group to any option you don't want available for general use. This will effectively hide the option from your users.

Security groups are set up using the Security Groups function. Users (and the security groups they belong to) are set up using the User function.

There are several areas within the system you can secure:

System Wide Access To Specific Functions

Using the System Security function you can control access to options that are generally available throughout the system. There are several options in this category:

For each option, you can indicate one or more security groups that have access to the option.

Access To Functions

When a function is selected from Main Menu, the system simply runs an executable program, the same as if it had been started from the operating system Start| Run command or Windows Explorer. This means it is important to secure access to the actual function, not the menu option.

For each function in the system, you use the Process function to control which security groups can run that function. If a user tries to run the function directly from the operating system, the security will still be checked to make sure access is allowed.

When the user runs Main Menu, they will only see options that the would have access to run. If all options in a sub-menu are not accessible then the sub-menu option will not be displayed for the user to select.

Access To Specific Controls Within A Function

Many screens within a function have fields and controls which can be secured. For example, the Delete button is often secured on data-entry screens. You can control access for the following:

To set up these security options, you start the function and select the Settings| Security menu option at the top of the window. (If you don't see the option, you may not have access to this function, see System wide access.) This will display a window which will allow you to add security groups to the fields and controls which can be secured for the specified window. You need to repeat this for each window within the function.

Point of Sale Options

It is possible to secure many different options within DynaPOS so that only certain users can perform various activities, for example change price, cancel sale, cancel item, and so on. Once again, we assign specific security groups to each security option. This is done via the Till. If a user attempts to perform an activity on the POS they do not have authority to perform, DynaPOS will allow a user who does have security access to carry out the function by logging in mid transaction and completing the task instead.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)