Administration and access

Administration establishes the operating environment. Changes can affect future transactions across several teams, so record the reason, verify the result, and communicate operational changes through your organization's normal process.

Know which screen owns a setting

Area	Application screen
Company identity and print profile	/admin/company-profile
Company feature configuration	/admin/general-settings
Branches	/admin/branches
Document/record numbering	/admin/numbering
Users and roles	/admin/users, /admin/roles
POS configuration and payment types	/admin/pos-settings, /settings/payment-types
Print layouts	/settings/print-layouts
GL posting mappings	/settings/gl-mapping
Order stages	/settings/order-stages
Import work	/admin/imports
Notifications	/admin/notifications

Give people the access they need

Create or maintain individual users and assign appropriate roles. Review company scope and intended operations. The menu table determines what is offered; the server separately protects actions. A broad-looking role name is not proof of access to restricted payroll operations.

Test a representative user account for the intended job. Confirm both that permitted work succeeds and that unrelated sensitive screens/actions are unavailable. Do not share one user's credentials among cashiers or use a real employee's account for training.

Configure numbering

Review the record/document type, series, prefixes, and current sequence before enabling automatic numbering. Existing documents must remain identifiable. A sequence setting is not permission to reuse historical document numbers.

After changing a series, create a demonstration record and verify the assigned number and duplicate handling. Do not manually reserve a production number by creating a fake financial transaction.

Set up print output

Company Profile supplies business identity data; Print Layouts controls supported presentation. Review both. Preview an authorized sample document, confirm company identity, currency, dates, item quantities, tax breakdown, totals, and page layout, then check the actual printer path used by staff.

Import records

Use the current template and supported import screen for the intended entity. Match codes, units, currencies, and required references. Start with a small demonstration batch, review errors, and compare saved records with the source file before loading the full set.

Check for duplicate codes and existing records before retrying an import. A partial failure does not necessarily mean no rows were saved. Preserve the import result and determine which records require correction.

Maintain controls

Review period configuration, posting rules, allowed document stages, branch/register relationships, and user access after a significant setup change. Verify the effect in a demonstration transaction. Some controls are company-level and others are item-, role-, or transaction-specific.

Change record

For each consequential change, retain the setting, previous value, new value, reason, approving person, effective date, and verification result in the organization's approved change record. The academy explains software behavior; the business remains responsible for deciding its operating policy.