End-user instruction center

Ticketing — ERPat User Guide

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.

Active modules48
Published guides395
SOPs3
Updated this month395
01Getting StartedBeginner-friendly first steps SOPStandard ProceduresRequired operational workflows AaLegends & FieldsStatus, badge, and field meanings Controls & ComplianceReview points and reminders

End-user guides from active ERPat modules

Showing 7 of 395 synchronized guides.

ticketing ×
Ticketing Reference Public

Data and Screen Reference

A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Ticketing module package.

Ticketing Reference Public

Getting Started

A practical first-run checklist for enabling Ticketing, granting the right permissions, preparing your starter data, and training the first users.

Ticketing Reference Public

Module Research Notes

Evidence gathered from the current Ticketing module files — controllers, models, configs, and migrations — before writing these user guide pages.

Ticketing Reference Public

Administration and Controls

How administrators keep Ticketing secure and reliable: permissions, menus, settings, public pages, API surfaces, migrations, and change management.

Ticketing Reference Public

Daily Operations

The routine operating manual for staff who run Ticketing day to day — the core screens, records, and workflows to use once setup is complete.

Ticketing Reference Public

FAQ and Troubleshooting

Answers to the most common setup, access, workflow, and support questions for the Ticketing module, with troubleshooting and support guidance.

Ticketing Overview Public

Ticketing

ERPat Events & Ticketing. Owns the Event Pass surface relocated out of core (passes, venue areas, seating blocks, seats, QR ticket rendering, approval/allocation/email-blast workflows) and is the foundation for the full Events & Ticketing platform (public checkout, payments, scanner check-in) mapped in specs/ticketing-module-implementation-spec.md. Owns its.