Sign in with your Supabase Auth account. Accounts are created and passwords set only via the Supabase dashboard — never in this app, never in code.
IT / Fraud & Tamper Overview
Signed in as — session ends automatically after 15 minutes of inactivity.
Below-Minimum Tickets
Fare or luggage recorded under the $1 USD / R20 ZAR floor — enforced app-side and by a database constraint, so any row here predates that fix or bypassed it directly.
Conductors Under 10 Tickets/Day
For the selected date range — a day this low is worth a look, not necessarily a problem.
Shifts With No Handover
Tickets exist but no shift report was ever submitted, 24+ hours later.
Unknown / Shared Devices
Unregistered devices, or one device used by more than one conductor.
Off-Hours Activity
Tickets issued before 05:00 or after 22:00 Zimbabwe time, for the selected date range.
Audit Log — Blocked Tampering Attempts
Every table here rejects UPDATE/DELETE for every client role — any row below is a real, blocked attempt, not routine activity.
Sequence Gaps — Possible Missing Tickets
A ticket number was assigned on a device but never reached the database.
Device Events — Kiosk / Tamper Signals
Lock-task exits, owner-PIN dialog attempts, and boot events, for the selected date range above.
Per-Conductor Risk Trend
Counts across all the signals above, per conductor, for the selected date range.
Handover Approval PIN
Separate from the manager login PIN — this one gates the offline shift-handover approval step on a conductor's phone, so it has to stay downloadable to their device. It still uses the legacy security password as its own extra confirmation step, independent of your IT sign-in above — this is a deliberate second gate on a sensitive write action, not an oversight.