Skip to main content

User Access and Authorisation

User Access and Authorisation​

Slide 11

Objectives​

Objectives

At the end of this session, you will be able to:

  • Understand and explain the purposes of and relationships between Users, User Templates, Roles and Privileges
  • Configure users and User Templates, including defining business functions and setting security requirements
  • Configure roles for POS and Estate Manager functions, including searching for and selecting privileges
  • Configure menus for POS and Estate Manager, including menu folders and function buttons, and setting embedded data in the menu item

Practical Exercises

  • Exercise 9 - Roles and Privileges
  • Exercise 10 - User Template
  • Exercise 11 - User
  • Exercise 12 - Menu Group
  • Exercise 13 - Menu

Configuration Topics​

This session covers the following configuration topics:

  • Users - individual user accounts
  • User Templates - templates representing job functions (e.g. Sales Associate)
  • Roles - sets of privileges for related functionality
  • Menus - POS and Estate Manager menus and menu groups

Architecture​

User Access Architecture

User, Role and Menu Relationships​

User, Role and Menu Relationships

EntityDescription
UserRepresents a person. Contains security settings such as password configuration. Is an instance of a User Template.
User TemplateRepresents a job function (e.g. Sales Associate). Contains settings applicable to all its members. Contains one or more Roles.
RoleContains all the privileges for a set of related functionality (e.g. returns, voids, sales functions). Links to a Menu.
PrivilegeRepresents the ability to execute or approve a function, e.g. Return an Item.
User Defined Privilege / Function Authorisation CodeUser-configured functions used to control access to reason codes and tender limits.
MenuMenu of functions to be executed at the POS or EM. Is a member of a Menu Group.
Menu GroupIdentifies the menus to be used at a specific location or device.

Exercise 9 - Roles and Privileges​

Discussion: Explain the following Enactor concepts: Privilege, Role, User Template

  1. Open Roles
  2. Create a new Role: Role Id = ROLE-TRAINx
  3. Enter: Description = TrainX Role - {your name}; Authorisation Level = 7
  4. Authorised Functions Tab: Package = Enactor POS; Process = Price Override; Apply Filters; Select Price Override Allowed; Select Authorises Price Override
  5. Special Functions Tab: Add function code TRAINX-FC; Add description; Select Add
  6. Save

Discussion: How would you check for enactor.pos.IssueGiftCardAllowed privilege?

Exercise 10 - User Template​

  1. Open User Templates
  2. Copy SALES_ASSIST_UK (UK Sales Assistant): User Template Id = USER_TEMPL_TRAINx
  3. Enter: Description = Train X User Template
  4. Roles Tab: Select your new role; Select Sales Assistant UK; Select Manager
  5. Save

Exercise 11 - User​

  1. Open Users
  2. Create a new User: User Id = XX.2 (TrainX number dot 2); User Template ID = Train X User Template
  3. Enter: Display Name = Your first name; Surname = Your last name; Location = UK Hertford
  4. Save; Enter a Password; Save

Discussion: If you forget your password, how can it be changed?

Exercise 12 - Menu Group​

This will be a group exercise

  1. Open Groups
  2. Edit Menu Group Id - All
  3. Select Standard_POS - Default Standard POS
  4. Select Add Menu Group: Menu Group ID = TRAINx; Description = TrainX Menu Group

Exercise 13 - Menu​

  1. Open Menus
  2. Set filters: Menu Set = POS; Role = Sales Assistant UK; Menu Group = Default Standard POS; Apply Filters
  3. Copy the SALE Menu: Menu Set = POS; Role = Your new role; Menu Group = TrainX Menu Group; Locale = (dash); Menu Id = SALE; Select Create
  4. If button in position 2, remove it
  5. Select SALE; Add Folder: ID = Products; Folder Label = Product Sales; Position = 2; Save
  6. Select "2 - Product Sales"; Add Button: Event = Sell Product; ID = Dress; Button Label = Sell Dress; Button Message Id = (remove); Button Message Base = (remove); Position = 1
  7. Data Tab: Name = enactor.mfc.ProductCode; Java Type = String; Value = RC6IDH1-11; Save
  8. Add Button: Event = Back Button; Position = 8; Save; Save

Discussion: How would you test your new menu?

Further Reading​

For additional information and further reading on User Access and Authorisation, please see the following guides:

DocumentDescription
How to: Configure Users, Roles & TemplatesConfiguring users, user templates, roles and privileges
How to: Configure Menu GroupsSetting up menu groups in the organisation hierarchy
How to: POS Menu Layout GuideReference guide for POS menu layouts and structure
How to: Configure MenusConfiguring POS menus, buttons, and events