Aspects
Technical requirements used by more than one feature.
Audit and monitoring
Oto provides activity and exception views for workflows that require accountability or reconciliation. These include the existing activity logbook and the action histories required for POS, stock, occupancy, child release, integrations, and hardware operations.
Read aspectAuthentication
Every staff account requires a phone number, which is its primary sign-in identifier. Oto normalizes phone numbers to include the applicable + country code. Email is optional and is not used as the primary identifier. Access links expire. Public forms use the token or code issued for that workflow. Returning camp families receive a six-digit code on the entered phone number before saved family details are shown or changed. Reception and employee kiosks use their documented activation, session, PIN, or face-identification flows.
Read aspectAuthorization
Oto uses scoped role-based access control with IAM-style permissions. The principal is the person or system requesting access. A role is a named collection of permissions. Each permission is written as service:resource:action, such as inventory:stock:adjust or messaging:inbox:assign. A scope limits the permission to the applicable operator, branch, department, or record relationship. Effective permissions are the permissions available to the principal after combining all assigned roles and scopes.
Read aspectService availability
Oto depends on cloud services, external providers, branch services, and installed devices. Workflows show whether the required service is available and whether an interrupted action completed.
Read aspectFiles and media
Oto features use files such as profile photos, child and pickup photos, knowledge documents, employment documents, signatures, receipts, wristbands, vouchers, and transaction exports.
Read aspectHardware
Oto supports the installed Zebra DS22 scanner, two 4B-2082A wristband printers, Welltech G4 receipt printer, three Xprinter units, two NEXGO N5 terminals, and two PAX A920Pro terminals. It retains their documented identifiers, addresses, protocols, and station roles.
Read aspectIntegrations and messages
Oto brings WhatsApp and Instagram conversations into shared customer inboxes and connects workflow records with configured accounting, payment, and support providers. Further messaging sources can be added later. Users see the provider status relevant to their task.
Read aspectAccessibility and locale
Oto displays dates, times, money, names, phone numbers, and translated content for the applicable branch and workflow. Forms and controls are usable across the supported staff, public, kiosk, and POS interfaces.
Read aspectTransaction safeguards
Oto prevents repeated or interrupted requests from creating duplicate payments, wallet entries, redemptions, attendance, stock changes, issuance, occupancy changes, or child-release outcomes.
Read aspectData and reporting
Oto provides the searches, reports, reconciliation views, and exports required by people, employment, events, POS, wallets, stock, occupancy, and other documented workflows.
Read aspectPrivacy and tenancy
Oto separates operator and branch operations while allowing the documented global member lookup. Visits, sales, payments, stock, events, bookings, check-ins, and device activity remain associated with the branch where they occurred.
Read aspect