Register and manage deposit accounts for a specified kiosk. A login lets a customer type an ID/password on the kiosk and go straight to depositing against one of the accounts below, without an interactive account lookup. One login can hold several accounts.

Not the same as "Corp Users" -- Corp Users are a separate, local login list stored on each kiosk itself (OpenKiosk admin → Corp Users). Logging in as a Corp User is just a local kiosk identity with no fixed account attached -- after login they still identify which account to deposit into through the normal RIB/client-code screen, same as any walk-in customer. A Deposit Account here, by contrast, is a fixed, already-verified customer account -- login skips straight to depositing, with no account lookup at all.

A plain staff login for the CUSTOMER-FACING kiosk deposit screen -- no bank account, RIB, branch code, or client code involved. Used by projects where the kiosk is a closed-loop cash drop for a fixed set of known staff (e.g. a franchise store manager depositing that day's takings), not a walk-in bank customer. This is the single source of truth for these accounts: they are created and administered ONLY here, on KioskManager -- never on the kiosk itself. The kiosk's own local admin panel can create a matching account as an offline fallback for when this server is unreachable, but that is never a second system to maintain in parallel with this one.

Not the same as "Deposit Accounts" -- Deposit Accounts (above) are real bank accounts with bank-side routing fields (ID/AGE/CLI/DEV/TEL) for a project depositing into individually-owned bank accounts. An Operator here has none of that -- just a login, a password, and a display name.

A CIT (Cash-in-Transit) officer visits a kiosk and empties the safe. Each collection is reported by the kiosk itself and logged here — it is not created from this dashboard.

Images or short videos shown on a kiosk after it sits idle. Assign to one kiosk, or leave unassigned to push to the whole fleet.

Straight from each kiosk's heartbeat — no setup needed. A kiosk appears here automatically once it reports in.

Optional asset records (serial numbers, firmware, warranty notes) for your own inventory tracking — separate from the live health above, which needs no manual entry.

Generate a single-use token here, then paste it into the new kiosk's admin panel under "Server Reg." to onboard it without creating the kiosk record manually.

Keys for third-party integrations calling into this server's API — separate from per-kiosk keys.

The database (kioskmanager.sqlite3) holds every kiosk, transaction, deposit account, user, and encashment record — this is the one file that actually matters for disaster recovery. Export takes a consistent live snapshot (safe to run anytime, even under normal traffic). Restore requires a follow-up restart to actually take effect.