Originally written by John Hardwick, last updated Oct 12, 2023, on the Swan Retail knowledge base (FRS).

---

Overview

SwanFRS offers the ability to protect certain actions which will require supervisor intervention to allow the activity to be access.  This document details how to control these features.

Configuration

This section details how to configure SwanFRS to operate with supervisory authorisation.

Application Parameters

To enable supervisory control, it will be necessary to define the appropriate application parameters.

USE_AUTHORISATION_OVERRIDE	Tick if you wish to force a user to seek authority if a protected task is attempted. i.e., Tick to turn on this feature.
USE_AUTHORISATION_OVERRIDE_PWD	Tick to force the entry of a password (the authenticating user’s login password).   Unticking will require the authenticating user’s login name to be entered, but will not force the corresponding password.

Restricted Roles

Privileges that trigger supervisor authorisation are: -

AMEND_PURCHASE_ORDER_LINE	An attempt was made to amend a purchase order line. (This includes cancelling as well as adjusting the quantities etc)
AMEND_STOCK_LEADTIME	An attempt was made to alter the ‘default’ lead time of a product.
CUSTOMER_REFUND	An attempt was made to refund payments to a customer.
DELETE_SO_LINE	An attempt was made to delete a sales order line where the sales order has previously been accepted.
DISCOUNT	An attempt was made to discount (alter the promotional selling price) of a product line of a sales order.
ORDER_FROM_SUPP_WHEN_STOCK_AV	An attempt was made to order product from the supplier when suitable product is already available in backing stock.
OVERRIDE_MINIMUM_DEPOSIT	An attempt was made to accept the sales order where a minimum deposit has not been taken.
SALES_ORDER_REFUND	An attempt was made to refund monies from a sales order.

Setting User Privileges

When building the user, it is possible to link the account with one or more role.  Each role has a series of privileges, each privilege allows access to a specific feature within SwanFRS.

To allow the user access to a feature the privilege must be ticked, unticking removes that feature from the role and there if that role is linked to the user is therefore blocked from the feature.

If the user has several roles within one role having feature X blocked and another having the same feature ticked, the user will be given access to feature X. I.e., ticked privileges supersede unticked privileges.

Changes to the role only take effect when the user next logs in.

Blocked Access

The ADMIN_HEADER role supersedes the authorisation control and should be removed from any ‘role’ where authorisation processes are to be used.

Whenever a user with this role attempts one of the ‘protected’ actions, a warning will be produced.

If access control is not required for one of the privileges, add this to the ‘allowed access’ column for the role.

Restricted Access

If the operator is to be blocked from performing a restricted role (as stated in Restricted Roles section of this document) ensure the role the user is linked to has the appropriate privilege(s) is / are unticked.

It is also important that the user’s role does not have the CAN_AUTHORISE privilege (i.e., unticked).

Supervisor Access

To generate a supervisor role, ensure the privileges (as stated in the Restricted Roles section of this document) are ticked (to allow access) and ensure the CAN_AUTHORISE privilege is also ticked.

Operation

Whenever an attempt is made to access a restricted feature, the system will generate one of the following warning pages.

Files from the Confluence page

• Supervisor Authorisation Guide.pdf