Demo data note: Screenshots in these docs use representative demo data. Do not use real customer records, secrets, payment keys, or private documents in public demos.
Key capabilities
Modern browser guidance keeps demos consistent across Edge, Chrome, Firefox, and Safari.
Demo-data notes help representatives avoid real customer data in screenshots and public calls.
Gated modules and detail routes are explained in user-facing terms so missing pages are not mistaken for product defects.
Support handoff steps capture useful context without passwords, tokens, local logs, or private implementation details.
Support handoff checklist
- Record the organization, user role, module, screen name, approximate time, and business impact.
- Capture a screenshot with sensitive information hidden or replaced by demo data.
- Write the exact steps taken before the issue appeared and whether it repeats after refresh/sign-in.
- Note whether the screen uses an add-on, a selected record, or a demo dataset that may not be enabled in every environment.
- Never send passwords, API keys, payment provider secrets, customer private documents, raw logs, or browser storage contents in a support handoff.
Browser requirements
Use a current version of Microsoft Edge, Google Chrome, Mozilla Firefox, or Safari. Enable JavaScript, cookies, and standard image loading. A laptop or desktop viewport is recommended for representative demos.
Demo and data expectations
Screenshots in this package use demo data. Empty states can appear in a fresh tenant until sample customers, vendors, products, contracts, rentals, and transactions are created.
Gated modules and the marketplace redirect
Optional modules (Rental, Manufacturing, CRM, Exhibition, Consolidation, POS, HR, and the Advanced feature sets) are governed by entitlements. If a module is not activated for the organization — or the user has no seat for it — its route is gated and the app redirects to the marketplace. This is expected behaviour, not a defect. To enable a module, an administrator turns it On under Settings → Module Access and assigns seats (see the Admin page). Some screens also need a selected record, or a separate kiosk application (POS), to display.
Common checks
If a page appears unavailable or empty, confirm in order: the user is signed in; the user has the right role; the module is activated and the user has a seat under Module Access; the browser is current; and the required demo record actually exists. Transient "service unavailable" or empty-KPI states usually clear on refresh — the dev environment rate-limits bursts of requests, so a moment's wait and a reload typically restores data.
A list seems to be missing recent records
Fixed on 8 August 2026. Lists throughout the system — invoices, customers, orders, quotations, credit notes, journal entries, vendor bills, payments, budgets, fixed assets, tax returns, contracts, rental assets and exhibition payment machines — previously stopped at the first 50 records, with nothing on screen to indicate that more existed. Depending on how a list was sorted, a newly created record could fall outside those 50 and appear not to have been saved at all.
Nothing was ever lost: the records were always stored correctly and were visible through search and reports. Lists now load in full, however many records they contain.
A page looks incomplete in Arabic, French or Spanish
Fixed on 8 August 2026. Until then, switching the interface language to Arabic, French or Spanish left the application without the data it needs to format numbers and dates. Any list containing an amount stopped rendering at the first one, so the page looked truncated rather than broken — the chart of accounts, for example, showed a single account group instead of all five, while the group heading still reported the full number of accounts it contained.
If you saw this, no data was affected: it was a display fault only, and the records were always intact. Reload the page once after updating and the full content appears. English was never affected.
The chart of accounts appears to be missing accounts
Fixed on 8 August 2026. The chart of accounts previously loaded only the first 50 accounts, with nothing to indicate that more existed. It now loads the complete chart whatever its size. The same limit applied to the account selection lists on invoices, bills, expense claims and payroll, which also now show every account.
Staying up to date (automatic)
The app keeps itself current. When a new version is deployed, open browser tabs detect it on their own and reload onto the latest build within about a minute — you do not need to manually hard-refresh or clear the browser cache after an update. Likewise, when an optional module's screens are updated, their widgets refresh in place without a full reload. If a page ever looks out of date, simply wait a moment or reload; as a last resort, Settings → Display → Reset app clears all cached data and reloads cleanly.
Screenshots
Use sign-in to explain browser and account readiness.
Use dashboard state to confirm the user reached the portal.
Use audit to discuss traceability when support needs context.
Use settings to confirm configuration area access.
Use installed modules to explain add-on availability.