Permissions

Permissions are used to control access to functionality within the features at the POS terminal, or within other business functions such as the POS Manager. Each function can have multiple levels of permissions.

This section provides information about how to grant permissions for individuals, groups, and departments for specific functions in the Configurator application.

Permissions can be granted for starting transactions, POS terminal functions including tender payment, tender return, non-merchandise sales and returns, and discounts. You can also grant permission to use a price below the minimum amount or over the maximum amount when selling or returning an open department item. Permissions allow you to configure security options such as password length requirements and maximum logon attempts.

Permission IDs identify a feature that is specific to an application type that has actions that require permission to be able to perform them.

Each store employee is assigned to a permission group. If employees are required in the employee database but do not need access to functions within the system, create a no permissions group and assign those employees to this group. On the Employee Maintenance window, the permission group is called an employee group. For more information about employee-related parameters, see the POS Manager User Guide.

For more information, see:

General
Screen Element	Description
Type	Entity type that you can set permissions for are as follows:User-Defined Transaction (UDT), User-Defined Function (UDF), or System (WKF) Note You can configure UDTs and UDFs for the POS terminal. All POS Manager functions are Employee Access and WKFs (well-known functions) that are configured for the POS Manager. WKFs are the same as UDFs and referenced by other permissions, except that they are not user-definable and cannot be customized. End of the note.
ID	Definition for the entity type. You can specify permission settings for the following: UDF — required to define permission settings UDT — required to define permission settings WKF — provides permission checking for transaction functions that either the UDF or UDT do not initiate
Action	This is specific to the user-defined function type, or to user-defined transactions. All user-defined functions must have permissions set to execute the action `Execute`. Some user-defined functions may have specific action requirements related to your function. You can specify different permission settings for each defined action requirement. Other functions are designed to support different permission requirements for different value levels or tiers; you must also specify the permission requirement for each defined level or tier. These levels are determined when the user-defined function type is created. If the user-defined function selected has one or several defined special actions requiring additional permission settings, you can see an extended list of special actions defined for the selected function. You can define a permission setting for each action individually, and execute the overall function. For more information about defined action types, see Permission Action Types
Access Type	The appropriate permission level for the selected action. Full access is required to perform this operation. For more information about defined access types, see Permission Access Types
Halo	Performs a function required for users that belong to a permission group (or role). If a cashier attempts to perform a function that they do not have the requisite permission for, a prompt displays requiring a HALO user to enter their User ID and Password for the restricted function to complete. If the action indicates `Override`, it performs a regular permission check and disregards the HALO requirement. If it indicates a HALO and Halo User information, Halo User permissions are checked to determine if the function can complete