Users and Roles

Users are created via the web console and must be assigned 'roles' which allow them to perform functions on the store terminal and on the console. There are three standard roles:

1) Enterprise Admin

This role permits access rights to all functions on the web console. The Enterprise Admin role does not have any access to the store/terminal.

2) Store Manager

Store Managers have access to all the functions on the terminal.

3) Operator

Operators have access to a limited set of functions on the terminal; sales, stock & timekeeping.


It is possible to assign a single user both a store and console role, however we recommend creating separate user accounts for store and back office functions, even if the same person accesses both. The reason for this is that the login function on the terminal is limited to the use of a numeric keypad to enter the passcode, as it is only required to provide local security against an opportunist attempting to access the terminal. This gives a workable compromise between security and ease of use.

The web console, however, is publicly available over the internet and so the password used for users with an Enterprise Admin role must be as secure as possible.

We recommend, for Enterprise Admin users, to create a user name / nick name that cannot easily be guessed - this adds a further level of security to the login details. 

In order to avoid the possibility of hackers using 'random guess' software to crack the login details, passwords for Enterprise Admin users should be at least 7 characters long and contain a mixture of:

  • upper and lower case letters
  • numbers
  • non alpha characters such as +, -, $, !, & or %

Store users (manager and operator roles) should be given a numeric password if the store staff will be using the touch screen numeric keypad to log on to the terminal. It is also possible to use a physical keyboard with the terminal which then allows a greater range of password characters to be used.


You can learn how to create new users here.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk