Documentation
Getting started
What Memoria is, how a school stands up its first event, and where to go next.
Memoria helps schools run high-volume student events without paper checklists, shared spreadsheets, or disconnected station logs. A school creates an event, imports a roster from existing systems, assigns stations, and watches completion status update live.
The core idea: events and stations
Everything in Memoria revolves around an event and its typed stations. The same application runs every distribution workflow — yearbook days, graduation tickets, senior checkout, device returns, and custom events — by configuration rather than by forking code. Each event type ships with a template that provisions the right stations, inventory, grants, and holds.
Two ways to run it
| Profile | Best for | How it runs |
|---|---|---|
| On-site / LAN | A single campus event with no dependence on internet | One host computer serves 12+ station laptops over the school network, fully offline. |
| Hosted / SaaS | Districts managing many schools centrally | Cloud accounts and realtime updates, with no on-site host to maintain. |
Stand up your first event
A school should be able to get a working event running in one setup session:
- Install Memoria on the host computer.
- Activate the school license.
- Create the first admin account.
- Create the event and apply its template.
- Import or paste the roster.
- Test one station flow.
- Run the event from station laptops on the same network.
Only two fields are required to import a roster: a participant ID and a name. Optional VIP and hold columns generalize fees, obligations, missing devices, or eligibility blocks. See Importing a roster.
Where to go next
- Installation & licensing — install the host and activate your license.
- Events & templates — create an event and configure it.
- Network setup — connect station laptops over the LAN.
- Event-day operations — a runbook for the day itself.