Home > Users > Screen Shots/Explanations > Users - Basic

Users - Basic

The Basic tab allows you to set up basic user information.

Figure: Example Users Screen

Full Name

The user’s full name.

POS Name

The name of the user as seen on the POS.

POS User Number

A unique number assigned to the user. A number is required if the user will be operating POS devices or you want to use the labour scheduling module. The Next Number button can be pressed to automatically assign a user number. It simply looks for the highest number currently in use and adds one to it.

When the user logs on to the POS, this is the log on number they will use.

If the User Number Is Mandatory option on the System tab of System Settings is checked on, this user number will be mandatory for all users.


The password assigned to the user. A password will be asked for when logging into the back office menu or when entering supervisor mode in DynaPOS. An option in the Till function allows the user to logon to DynaPOS via this password. This is useful when using a security device such as cards with a magnetic strip. The number on the security device is entered as the password for the user. When the DynaPOS asks for the user to logon, the user can swipe their card. The system will attempt to log on using this number as the user number. If it is not successful it will then attempt to log on using this number as the password.

POS Swipe Card

This option can be useful if using logon cards with Magnetic Swipe Readers (MSRs) or scanners. The Password field can contain a password used for logging in at back office and the POS Swipe Card field can contain the MSR data, to be used for the POS logon.

If this field is not filled in, POS will simply use the Password field. If this is filled in, it must be used to log on at POS. You cannot use this or the Password to log on to POS. The exception to this, is if you are using POS in handheld mode. In this case the swipe card will not be available and so the normal Password field.


The primary location this user belongs to. For your head office/administration staff, you should set up a location code called 'HO' as an 'Admin' type location and assign the users to that location. Users must be assigned to a location.


If the user will log in to the back office menu, they must be assigned a Menu code. This is the code of an existing menu definition which will control what options the user will see on the menu. When adding a new user, the menu code will default to the menu defined in the Defaults tab of System Settings. The user editing the details must be authorised for the selected menu and the user being edited must be authorised for the selected menu. A user is considered authorised if they are in any of the security groups that have been associated with a particular menu.


This identifies the commission to be used by this user. If this is left empty, the system uses the commission code set on the location.

Buyer Code

The buyer code to which the user belongs. If set, this will control the items that a user is allowed to see and order.


The phone number of the user.


The mobile phone number of the user.


The fax number of the user.


The email address of the user.

Date Of Birth

The date of birth of the user.

Purchasing Authorisation Level

Only shown if the Use Purchasing Authorisation Levels check box is selected in the Inventory tab of System Settings to indicate Purchasing Authorisation Level functionality is enabled.

The list of available levels is populated once a location has been chosen. The list is determined by the location selected. If no authorisation levels are configured for the location, the system works up the location hierarchy to find the first set of configured levels. If authorisation levels are set, only the 'no limit' user for that location can set the other users authorisation levels.

The POS Button can be used to send the user details to the POS immediately. When you press the button, the system will send the user code to each of the locations listed on the POS tab.

The Copy Button can be used to clone the User.

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