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 7 of 478 synchronized guides.
Overview of the ERPat Security module — the administrator toolkit for banning sign-in devices, granting offsite-access windows, recovering locked accounts, controlling live sessions, and reviewing access-device logs, built on top of ERPat's core protection layer.
Frequently asked questions and troubleshooting for the ERPat Security module — banning and restoring sign-in devices, why the module can't be disabled, offsite-access grants, unlocking accounts, terminating sessions, access-device credentials, and audit logging.
Administer the ERPat Security module — the single always-on module_security setting, the eight permission groups covering Device Management, Offsite Access, Locked Accounts, Active Sessions and Access Logs, the four-item Security menu, and audit logging of every sensitive action.
Step-by-step daily procedures for the ERPat Security module: find and ban the devices staff sign in from, grant and revoke offsite sign-in windows, unlock locked accounts, view and terminate live login sessions, and register, credential, and audit access devices.
Enable the ERPat Security module, run its migrations, confirm the always-on umbrella setting, and grant the Device Management, Offsite Access, Locked Accounts, Active Sessions, and Access Logs permissions so administrators can start using all four tools.
Technical reference for the ERPat Security module — controllers, routes, models, views, migrations, database tables and columns, permission keys, menu entries, and system-audit-log event keys for Device Management, Offsite Access, Locked Accounts, Active Sessions, and Access Device Logs.
Research evidence behind the ERPat Security user guide — the live module source files (manifest, config, controllers, models, migrations, views, language) read to verify every fact about all four tools, including the Device Management move in from core.