Workstation and Instance Settings
Control this computer’s POS experience, Quick Launcher, and diagnostic logging.
- Configure This Workstation's POS Experience
- Configure the Quick Launcher
- Configure Diagnostic Logging Safely
Configure This Workstation's POS Experience
How to Configure This Workstation's POS Experience in Muhasib ERP
Overview
This guide will help you configure POS display, item selection, search columns, temporary-sale behavior, and Quick Pay for this computer.
New POS sessions on this computer use the local selection/display/payment behavior. Company-wide POS settings still apply and can override or complement outcomes.
Who can do this
You need access to Instance Settings plus authorization for local payment and transaction behavior.
Before you start
Record current local settings. Close POS, identify screen resolution/scaling, and prepare approved payment type plus cash/card payment accounts.
Where to find it
Back Office → Settings → Instance Settings → POS Module Settings.
Configure This Workstation's POS Experience
Step 1: Choose automatic POS size or enter the approved manual size
Step 2: Choose the supported current interface; treat UI 2 marked beta
Choose the supported current interface; treat UI 2 marked beta as test-only unless approved.
Step 3: Configure item-search style and visible columns: ID, barcode, name, quantity,
Configure item-search style and visible columns: ID, barcode, name, quantity, selling price, available stock, SKU, UPC, brand, and image as available.
Step 4: Configure prompts for quantity, price, or line-item options after selection
Step 5: Configure barcode/name display and POS minimize behavior
Step 6: Configure temporary sale/default behavior only when entitled
Step 7: For Quick Pay, enable it and select default payment type,
For Quick Pay, enable it and select default payment type, cash account, and card account.
Step 8: Save, close, and reopen POS
Check your work
Run a disposable cash and card sale, check prompts/search columns/layout, and compare and confirm the correct payment accounts.
If something goes wrong
- Restore the previous local values if POS becomes unusable.
- Do not enable beta UI on production terminals without approval.
Related guides
What to do next
Configure the Quick Launcher
How to Configure the Quick Launcher in Muhasib ERP
Overview
This guide will help you select a small set of authorized shortcuts for this workstation.
Selected values are saved locally. Visibility still depends on role, plan, company, and target-form availability.
Who can do this
You need access to Instance Settings plus access to each destination task.
Before you start
List the user's most frequent authorized tasks. A shortcut does not grant permission or satisfy prerequisites.
Where to find it
Back Office → Settings → Instance Settings → Quick Launcher Settings.
Configure the Quick Launcher
Step 1: Review available transaction, master, inquiry, and report shortcuts
Step 2: Select only tasks used on this workstation
Step 3: Keep the selection at or below the form's validated maximum
Keep the selection at or below the form's validated maximum of eight until the target build proves otherwise.
Step 4: Save the instance settings
Step 5: Return to or restart Back Office if required
Step 6: Open each shortcut and confirm its destination
Check your work
Confirm the intended shortcuts appear and unavailable tasks remain blocked.
If something goes wrong
- If the visible launcher ignores these selections, record the system build and treat the form as legacy/unwired pending confirmation.
Related guides
- Use the Muhasib Quick Launcher
- Configure This Workstation's POS Experience
- Audit a User's Effective Access
What to do next
Configure Diagnostic Logging Safely
How to Configure Diagnostic Logging Safely in Muhasib ERP
Overview
This guide will help you enable only the diagnostic detail needed for a controlled investigation, then return logging to its normal level.
The logging framework can emit more detail, increasing storage, privacy exposure, and performance cost.
Who can do this
You need access to Instance Settings and authorization to collect diagnostic or tax-integration data.
Before you start
Identify the issue, reproduction window, approved log destination, retention period, and fields that must be redacted.
Where to find it
Back Office → Settings → Instance Settings → Log Settings.
Configure Diagnostic Logging Safely
Step 1: Record current logging options
Step 2: Select only required levels: Error, Warn, Info, or Debug; use
Select only required levels: Error, Warn, Info, or Debug; use All only for a short approved capture.
Step 3: Enable debugging only when requested by authorized support
Step 4: Enable Tax Logs only in a sandbox or under approved
Enable Tax Logs only in a sandbox or under approved sensitive-data handling.
Step 5: Save and restart if required
Step 6: Reproduce the issue once
Step 7: Collect and sanitize the relevant time window
Step 8: Restore normal logging and remove temporary sensitive copies according to
Restore normal logging and remove temporary sensitive copies according to policy.
Check your work
Confirm the required event appears without credentials, tokens, personal data, or unnecessary transaction content.
If something goes wrong
- Never publish raw logs.
- Do not leave Debug/All/Tax logging enabled indefinitely.