Roles and Device Control

Protect The Sensitive Part First

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Roles and Device Control narrows that work to who may export, operate, import, reconcile, and hold EMS LAN devices or files. Because this is a safety page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What Needs Protection

This page is about reducing harm before offline files, roles, devices, or private records are handled. Read it before speed or event pressure pushes the team into shortcuts. The intended readers are Event leads and Partner admins. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/offline-snapshot?id=:eventId.
• Records or contracts involved: Role assignments and Device custody notes.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Check Custody Before Continuing

1. Name the sensitive file, role, device, or record: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Roles and Device Control.
2. Confirm who is allowed to hold or change it: Use /rego/events/manage/offline-snapshot?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Record custody and approval before the next step: Keep Role assignments and Device custody notes in view so the work stays tied to the records or contracts it can affect.
4. Escalate gaps before the event depends on the result: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

The Work Is Safe Enough To Continue When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook before assigning LAN work.

1. Step 1 - Identify the person, device, file, and event. Confirm the event lead and partner admin approve EMS LAN operation. This establishes authority.
2. Step 2 - Limit access before work starts. Assign separate owners for export, LAN device operation, import, and reconciliation when possible. This reduces unchecked power.
3. Step 3 - Apply the control rule. Give devices and files only to named operators. This creates custody.
4. Step 4 - Treat exceptions as incidents. Remove access from people who no longer need it and stop operation if a device is missing. This protects records.
5. Step 5 - Record custody or deletion proof. Record operator names, device IDs or labels, and handoff times. This supports audit.
6. Step 6 - Return authority to the event lead. Confirm every device and file returned or has an approved final disposition. This closes custody.

Role model

Role	Allowed EMS LAN responsibility
Partner admin	Approves export/import authority and high-risk decisions.
Event lead	Declares LAN active, assigns owners, and accepts closeout.
LAN operator	Operates assigned device and reports issues.
Import operator	Imports final returned file only.
Reconciliation operator	Proves dashboard records after import.