Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 395 of 395 synchronized guides.
Quick fixes for the register problems cashiers hit most often, from missing menus and closed shifts to stock blocks and discount errors.
Answers to the questions security teams ask most about ERPat Patrol, a plain-language glossary (blotter, chain of custody, legal hold, DSAR, retention, tracking code), and fixes for missing menus, silent alerts, disabled AI, undeletable assets, and lost public tracking codes.
The verification trail behind the ERPat Patrol guide: the actual controllers, models, database tables, migrations, cron jobs, config files, and public endpoints each documented claim was checked against.
Evidence gathered from the current Notes module files — controllers, models, configs, and migrations — before writing these user guide pages.
Data and screen reference for the Movements module: all six database tables and their key columns, controllers and routes, cron jobs, system-log events, statuses, permissions, and the mobility policy rule engine.
A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Tenancy module package.
A practical first-run checklist for enabling Tenancy, granting the right permissions, preparing your starter data, and training the first users.
Evidence gathered from the live Movements module source before writing this guide — the exact configuration, controller, model, migration, cron job, and seeder files read, and what each one proves about the module's behavior.
Enable the ERPat Movements module: run its module migrations, turn it on in Manage Modules, grant the Human Resource: Mobility permissions, understand the seeded mobility policy defaults, and load the demo data.
Evidence gathered from the current Lending module files — controllers, models, configs, and migrations — before writing these user guide pages.