# Troubleshooting, browser requirements, and support handoff

> Screenshots in this page use demo data and are intended for representative/user-facing documentation.

Representative-safe guidance for browser readiness, demo data expectations, gated modules, screenshot limitations, and support handoff without exposing secrets.

[← Public docs landing](README.md) · [Open HTML version](troubleshooting.html)

## 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

1. Record the organization, user role, module, screen name, approximate time, and business impact.
2. Capture a screenshot with sensitive information hidden or replaced by demo data.
3. Write the exact steps taken before the issue appeared and whether it repeats after refresh/sign-in.
4. Note whether the screen uses an add-on, a selected record, or a demo dataset that may not be enabled in every environment.
5. 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 and detail pages

Some screens need a selected record, installed add-on, or separate kiosk application. The public screenshot set focuses on representative-safe list, dashboard, setup, and workflow screens.

## Common checks

If a page appears unavailable, confirm the user is signed in, has the right role, the add-on is enabled, the browser is current, and the required demo record exists.

## Screenshots

| Screen | Demo note | Image |
|---|---|---|
| Login | Use sign-in to explain browser and account readiness. | ![ColorsX74 ERP Login screen with demo data](assets/screenshots/web/login.png) |
| Dashboard | Use dashboard state to confirm the user reached the portal. | ![ColorsX74 ERP Dashboard screen with demo data](assets/screenshots/web/dashboard.png) |
| Audit log | Use audit to discuss traceability when support needs context. | ![ColorsX74 ERP Audit log screen with demo data](assets/screenshots/web/audit.png) |
| Settings general | Use settings to confirm configuration area access. | ![ColorsX74 ERP Settings general screen with demo data](assets/screenshots/web/settings-general.png) |
| Installed modules | Use installed modules to explain add-on availability. | ![ColorsX74 ERP Installed modules screen with demo data](assets/screenshots/web/marketplace-installed.png) |

## Related pages

- [Overview, login, and dashboard](overview.md)
- [Accounting, reports, banking, tax, and payments](finance.md)
- [Sales, purchase, contracts, and rental](commercial.md)
- [Inventory, manufacturing, marketplace, and add-ons](operations.md)
- [AI, Copilot, setup wizard, scan, draft, and settings](ai-automation.md)
- [Admin, settings, security, audit, approvals, and notifications](admin-security.md)