Chapter 7

Security

Quasar provides a layered security model that controls who can log in, what screens they can see, and what actions they can perform. This chapter covers the three layers: Users, Security Types, and POS Security Levels.

The Security Layers

Security in Quasar operates at two distinct levels:

Layer	What It Controls	Where to Configure
Back-Office Security	Login to the Quasar accounting client — which screens, reports, and actions each user can access	User Master + Security Type
POS Security	Login to the POS terminal — cashier vs. manager vs. supervisor capabilities	Employee Master (Point-of-Sale tab)

Both layers are independent. An employee might have Supervisor access at the POS but only Bookkeeper access in the back-office, or vice versa.

Users

A User is a login account for the Quasar back-office application. Each user has:

Field	Purpose
Name	Login username (must be unique)
Password	Case-sensitive password
Employee	Links the login to an employee record
Store	Default store — pre-selected at login
Security Type	Determines what this user can do
Screen	Default screen shown after login

Create users at Setup → System → Users. See User Master.

Every User Needs an Employee A user must be linked to an employee record. Create the employee first (see Chapter 6), then create the user and link them together.

Security Types

A Security Type is a named permission profile that you assign to one or more users. It controls access at two levels:

Rules — Screen-Level Access

The Rules tab defines which screens each user can access and what operations they can perform:

Permission	What the User Can Do
View	Open and read the screen (read-only)
Create	Create new records
Update	Edit existing records
Delete	Remove records

Rules are evaluated in order — the first matching rule wins. You can use a wildcard rule at the bottom to set a default (e.g., “View only for everything not explicitly listed”).

Flags — Fine-Grained Permissions

The Flags tab controls specific business operations that go beyond basic screen access. Key flags include:

Flag	What It Controls
SELLING_PRICE_OVERRIDE	Can override selling prices on invoices
CREDIT_LIMIT_OVERRIDE	Can sell to customers over their credit limit
CREDIT_HOLD_OVERRIDE	Can sell to customers on credit hold
GLTX_CHANGE_DATE	Can change the posting date on transactions
CHANGE_CHEQUE_PRINTED	Can modify cheques after they have been printed
CHANGE_EMPLOYEE	Can change the employee assignment on transactions
CHANGE_EXTRA_DATA	Can modify extra data fields on master records
ADD_TASKS_OTHER	Can assign tasks to other employees
INQUIRY_HIDE_ACCOUNT	Hides the Account tab in the Inquiry screen
INQUIRY_HIDE_CUSTOMER	Hides the Customer tab in the Inquiry screen
INQUIRY_HIDE_VENDOR	Hides the Vendor tab in the Inquiry screen
INQUIRY_HIDE_ITEM	Hides the Item tab in the Inquiry screen

Use the Clear All, Set All, and Toggle buttons to manage flags quickly. See Security Type Master.

Planning Security Types

Start by thinking about the roles in your organization and what each role needs access to. Common security type configurations:

Security Type	Rules	Flags
Administrator	Full access to all screens (View, Create, Update, Delete)	All flags enabled
Manager	Full access to operational screens; restricted access to system setup	Price override, credit overrides enabled
Bookkeeper	Full access to ledger, AR, AP; no access to inventory setup or system configuration	Date change enabled; employee change disabled
Data Entry	Create and update invoices, receipts, and orders; no delete permission	No overrides
Read Only	View all screens; no create, update, or delete	All flags disabled

Tip Start with a small number of security types and add more only when needed. You can always copy an existing type and adjust its permissions to create a variation.

POS Security Levels

POS security is separate from back-office security. It is set on the Employee Master Point-of-Sale tab and uses a tiered level system:

Level	Capabilities
No Access (0)	Employee cannot log in to the POS
Cashier (1)	Ring sales, process returns, apply discounts, handle tenders
Manager (2)	Cashier functions plus: void entire sales, post voids, payout transactions, ringoff, training mode, override tender limits and credit limits
Supervisor (3)	Full access including: system configuration, reset till, clear/load files, set date, exit POS, shutdown, remote access

Each POS function is assigned a minimum security level. When an employee attempts a function above their level, Quasar prompts for a manager override — a manager or supervisor can enter their password to authorize the action without logging out the current cashier.

Key POS Security Settings

Function	Default Level	Why
Sell Item / Tender	Cashier	Basic sales operations
Void Line	Cashier	Remove a line item from the current sale
Void Sale	Manager	Cancel an entire transaction
Post Void	Manager	Void a previously completed sale
Payout	Manager	Cash paid out from the till
Ringoff	Manager	End-of-shift cash count and close
Configuration	Supervisor	POS system settings
Reset Till / Exit	Supervisor	Critical system operations

POS Security Is Configurable The default security levels can be customized per site through the POS configuration. For example, you can raise “Void Line” to Manager level if you want to prevent cashiers from removing items without authorization.

Security Setup Checklist

Plan your Security Types based on organizational roles
Create the security types at Setup → System → Security Types
Set Rules (screen access) for each type
Set Flags (business operation permissions) for each type
Create Users at Setup → System → Users, linking each to an employee and assigning the appropriate security type
Set POS Security Levels on the Employee Master for each employee who will use the POS
Customize POS security defaults if the standard levels need adjustment

Do Not Share Logins Every person who uses Quasar should have their own user account and POS password. Shared logins make it impossible to audit who performed a transaction, void, or override. The audit trail is only as good as the login discipline.

What’s Next?

Chapter 8 — Importing data (items, customers, vendors)