Requirements
Check these points before you install the app. None of them involves Helpifyr.
Platform
| Requirement | Detail |
|---|---|
| Frappe and ERPNext | A supported v16 bench. The app is built for ERPNext v16 and is not usable without ERPNext. |
| Database and queues | Healthy MariaDB and Redis, with working scheduler and queue workers. Outbox delivery, the ingestion queue, and periodic jobs depend on them. |
| Shell access | Access to the bench and the ability to run bench commands for the target site. |
| Backup | A complete site backup, taken before you install, migrate, or upgrade. |
| App code in every runtime | If your bench runs backend, scheduler, and queue workers as separate containers, the app code must be present in every one of those images. |
Reference bench and tested versions
The project's reference bench is pinned to the vendor image frappe/erpnext:v16.22.0 by digest. That image bundles ERPNext 16.22.0 and Frappe 16.20.0. The pin is recorded in contracts/repository/reference_image_pin_v1.json in the source repository.
Be aware of what this means:
- The project's installation and acceptance evidence is produced against this reference bench. Other v16 patch levels are not covered by that evidence.
- ERPNext 16.22.0 is below the ERPNext 16.23.0 security patch (advisory GHSA-p577-cxv9-h82f). The project owner accepted this for the reference bench only. For your own production bench, follow the ERPNext and Frappe security advisories and plan your patch level yourself.
- One known exception exists: the project's performance baseline was measured on a newer image (
v16.32.3) and has not yet been re-measured on the reference pin.
Site and organisation
- One ERPNext Company per broker legal entity. Activation is configured per Company.
- Multi-company use on one site is intended only for controlled, related legal entities. Mutually unauthorised broker organisations need separate sites.
- A named operator with the
Insurance Broker Administratorrole for activation and readiness checks (see First steps and activation). - Maker and checker roles for commission work must be held by different people.
Decisions you need to make before activation
The app installs inactive on purpose. Activation needs reviewed inputs from you:
- country and isolation mode of the Company;
- registration and role evidence;
- privacy configuration (processing purposes, legal bases);
- tax review reference and accounting strategy (default
None); - security, backup, and test export and import evidence.
What you do not need
You do not need a Helpifyr account, a Helpifyr runtime, or any external provider. The app does not call Helpifyr services for installation, activation, privacy workflows, backup, restore, import, or local operations.
Not demo software on production
Never install synthetic demo data on a production site.
Next step
Continue with Installation.